[Bug 2078597] Re: Failed to flush binfmt_misc rules, ignoring: Permission denied

2024-09-10 Thread Hadmut Danisch
No, I need to run podman/docker inside. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078597 Title: Failed to flush binfmt_misc rules, ignoring: Permission denied To manage notifications about thi

[Bug 2078597] Re: Failed to flush binfmt_misc rules, ignoring: Permission denied

2024-09-10 Thread Nick Rosbrook
Are you able to run unprivileged containers instead? That would be the suggested configuration from upstream LXD. There are many things that do not work with systemd in privileged LXD containers due to AppArmor etc. Upstream systemd does not like adding workarounds for issues caused by AppArmor ru

[Bug 2078597] Re: Failed to flush binfmt_misc rules, ignoring: Permission denied

2024-09-10 Thread Hadmut Danisch
security.nesting: "true" security.privileged: "true" But maybe looking for /proc/sys/fs/binfmt_misc may be the trap, because it is not just a matter of beeing mounted and rw, there's also some trouble with apparmor. E.g. on the machine # ls -lF /proc/sys/fs total 0 -rw-r--r-- 1 roo

[Bug 2078597] Re: Failed to flush binfmt_misc rules, ignoring: Permission denied

2024-09-10 Thread Nick Rosbrook
systemd-binfmt should just exit when /proc/sys/fs/binfmt_misc is not mounted rw, which I thought was usually the case in LXD containers. Are you running a privileged or unprivileged container? ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Imp