Thanks, Nish. My thoughts: 1.a sounds good
1.b i'd like another way to do that, but not sure what a better way would be. 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. 1.d CAP_ADMIN_READ is not a real capability. So if 1.d is fixed by that, then something else is wrong. -- 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
