After reading a bit more about this issue, I can see where the conflict
happens:
1/ systemd requires any container manager to mount /sys read-only,
according to https://systemd.io/CONTAINER_INTERFACE/ in order to make
udevd behave properly.
2/ NetworkManager checks for /sys to be read-only in
This should have been fixed upstream by:
https://github.com/systemd/systemd/pull/18559
Or https://github.com/systemd/systemd/pull/18684 and
https://github.com/systemd/systemd/pull/18717 respectively. I wonder why
this fix isn't working for network-manager, while it seems to be good
for LXD?
--
This bug was fixed in the package network-manager - 1.32.2-0ubuntu2
---
network-manager (1.32.2-0ubuntu2) impish; urgency=medium
* debian/patches/ubuntu_revert_systemd.patch:
- restore the workaround for the systemd and lxd issue, it's still
needed (lp: #1936312)
--
Thanks Lukas, I hadn't noticed that the systemd was reverted, I added
back the nm change for now
** Changed in: network-manager (Ubuntu)
Status: New => Fix Committed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because
Related to: LP: #1914062
Two patches exist, both were dropped from their corresponding packages:
https://git.launchpad.net/network-manager/commit/?id=4c4f7172
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?h=ubuntu-
impish=efebddfe37efff6a259ef7fd59212d65ad1b848b
--
