Sometimes, I don’t know why and when and how, the container according to LXD is still in use.
As suggested on github I did a bit debugging this crap out of it
I can reproduce this on different systems, all running ubuntu 20.04 with different kernels and different operating systems. But until now, I don’t know the fuck what is causing it.
I would like to shoot it in the face but I don’t know where its.
Maybe someone has a suggestions, so far someone did suggest I shall turn it off and on again until suddently it shits itself.
I try this later, if someone else has a better suggestion, lemme know.
Thanks guys
Please can you provide output of sudo nsenter --mount=/run/snapd/ns/lxd.mnt -- cat /proc/mounts please.
For 2:
Can you reboot the machine so you have a fresh mount table and then try starting and stopping the container until the problem arises. At that point can you provide a copy of /var/snap/lxd/common/lxd/logs/lxd.log for debugging.
@stgraber any ideas on this one, the host sees the volume mounted but cannot unmount it, and the snap mount namespace doesn’t see the volume mounted (hence why its trying to mount it).
I rebooted the system as suggested and try to re produce the bug right now by starting and stopping it.
As soon it hangs again, I let you know.
So far the script restarted the container 120 times, no issue yet.
I will check if I find a stuck container somewhere else, and give you the output when I get to it.
Something caused some repeated overmounting of the shmounts directory somehow…
Can you show journalctl -u snap.lxd.daemon -n 500 as well as snap changes?