Skip to content

Ghost containers on a Swarm docker node running Sysbox #914

@arp-mbender

Description

@arp-mbender

I'm running 0.6.6 CE of Sysbox on a Swarm-connected docker node. Generally - everything seems fine when I start a swarm service using this node.

However I've noticed, after a week or two, that the number of active containers on this node is higher than expected. After stopping all the services I found a couple of containers are still running. Re-creating the service (i.e. running docker compose down and up) does not clean up these containers.

These containers "work" - there's no error in their operation. The issue is the fact they exist at all, seemingly apart from the docker service responsible for their creation. I'm not sure at which point this happens - probably somewhere when swarm re-creates containers after one's stopped, but I've no idea if that's the case.

Does this seem like something sysbox-related?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @arp-mbender

        Issue actions

          Ghost containers on a Swarm docker node running Sysbox · Issue #914 · nestybox/sysbox