>> 1.c does lvm also fail in privileged containers? I can see no use to >> running it (for now) in an unprivileged container, so the same solution >> as 1.a seems reasonable. > > It also fails in privileged containers in the same way (see 2.b in > comment 20). Note that it works if I manually start the socket after > boot.
It seems /lib/systemd/system/lvm2-monitor.service also needs the "ConditionVirtualization=!container" line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576341 Title: systemd in degraded state on startup in LXD containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
