Tom Parrott
Tom Parrott
Most likely related to similar issue with Incus https://github.com/lxc/incus/issues/791#issuecomment-2083765381
> # Required information > > * Distribution: Ubuntu > > * Distribution version: 24.04 > > * The output of "snap list --all lxd core20 core22 core24 snapd": >...
Does this fix it inside the container ln -s /etc/apparmor.d/runc /etc/apparmor.d/disable/
Also what does `sudo cat /proc/sys/kernel/apparmor_restrict_unprivileged_userns` Show both on the host and inside the container?
What do you see in dmesg re apparmor after that?
Thanks! Please can you add a test to https://github.com/canonical/lxd-ci/blob/main/tests/storage-vm so that we can ensure this fix is backported to the other tracks.
Thanks for your report. We will endeavour to investigate this soon. I'm not sure why the files are all modified, although I suspect its to do with ensuring all files...
> We encounter the "no such file or directory" error now regularly and have no other option than to retry, which is a bummer for an operation which can take...
See if https://github.com/canonical/lxd/pull/13815 helps once it lands in latest/edge. To be clear im not rejecting your PR, but in isolation I don't believe it will prevent the "no such file...
> Only then the "file walk" should be required. My PR would fix performance and also "not found" errors for my use case, because the "file walk" would never happen...