Closed jalbstmeijer closed 1 year ago
This happens when you delete the snap specific folders in your host's /tmp. Sometimes it's user error which causes that, or time, it's some kind of cleanup script or daemon on your system which similarly doesn't know what it's doing and is deleting the snap temporary storage.
When this happens, /tmp
inside of the snap environment becomes completely broken. Only way to fix that is a full snap restart or system reboot.
@stgraber
Yes, you repeat what was stated in https://github.com/lxc/lxd/issues/5650
You seem to have missed this remark.
"While still being able to stop containers, I have tried to find these /tmp/lxdconfig* files, but I can't. Where should they be in a snap install of LXD?"
find /tmp/snap.lxd/
/tmp/snap.lxd/
/tmp/snap.lxd/tmp
This location is now empty, but I can still stop a container, without an error. So when will it stop working?
Those are temporary files, they only exist for a few milliseconds. The problem is when the directory itself has been deleted as that can't be re-created without a full snap restart.
Issue description
After a while I can not stop a container anymore. Seems like I have a similar issue as in the closed issue report https://github.com/lxc/lxd/issues/5650
I have not been able to identify a process cleaning up /tmp on the server as suggested in the issue report mentioned. I wonder if LXD auto snap updates might trigger this issue.
While still being able to stop containers, I have tried to find these /tmp/lxdconfig* files, but I can't. Where should they be in a snap install of LXD?
Steps to reproduce