Ghost containers on a Swarm docker node running Sysbox

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?

Start by reproducing the report with Sysbox 0.6.6 CE on a Docker Swarm-connected node, then compare active containers before and after stopping and recreating the service with docker compose down and up. Done means determining whether the orphaned containers are Sysbox-related and identifying when they become detached from the responsible service.