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 rules, and upstream LXD (from
what I understand) does not want to spend a lot of effort supporting
privileged containers, when unprivileged containers are the more secure
alternative.
For those reasons, I am going to mark this "won't fix." If running
unprivileged containers does not work for you, I would suggest either
masking the systemd-binfmt.service unit in your containers, or follow up
with upstream(s) about the issue.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
--
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078597/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
