Closed falstaff1288 closed 5 years ago
The reason for this is that you or some daemon/script on your system decided to cleanup /tmp on the host, removing the snap-specific temporary directory which is used by LXD.
Doing so breaks /tmp in the snap environment and prevents any temporary file from being created by LXD. This causes what you're seeing above as well as a large number of other issues.
There is no way to fix this while LXD is running and snapd doesn't make it easy to fix that even if you stop LXD entirely, the easiest way out of this is to reboot and then make sure you don't have something wipe anything that says snap
in /tmp.
@stgraber Is there any way to move thoese config file into another folder which won't get cleaned?
Those aren't config files, they are temporary copies of files being copied in and out of the container.
/tmp is by all definitions the correct location for this. Now if the user or a tool they're using goes and deletes files from the filesystem that they didn't themselves create, it's not too surprising that things may break.
Those aren't config files, they are temporary copies of files being copied in and out of the container.
/tmp is by all definitions the correct location for this. Now if the user or a tool they're using goes and deletes files from the filesystem that they didn't themselves create, it's not too surprising that things may break.
You can check journalctl
whether systemd-tmpfiles-clean
or similar has run. That would be a suspect.
Required information
Issue description
The snap package for lxd was automatically updated to 3.12. Since then, I am getting the error reported above.
Steps to reproduce
Output example