Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ghost containers on a Swarm docker node running Sysbox #914

Open
arp-mbender opened this issue Feb 12, 2025 · 0 comments
Open

Ghost containers on a Swarm docker node running Sysbox #914

arp-mbender opened this issue Feb 12, 2025 · 0 comments

Comments

@arp-mbender
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant