[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

Nish Aravamudan nish.aravamudan at canonical.com
Wed Mar 29 23:21:29 UTC 2017

On 29.03.2017 [03:19:16 -0000], Serge Hallyn wrote:
> 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.

Yeah, I spent some time looking at the CPC generater and it seems like
this is pretty hard-coded:

## --------------
# for maverick and newer, use LABEL= for the '/' entry in fstab
if [ -n "${root_fs_label}" ]; then
   sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1," "${rootd}/etc/fstab"
cat > /etc/fstab << EOM
LABEL=cloudimg-rootfs   /   ext4 defaults 0 0

> 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

> 1.d
> CAP_ADMIN_READ is not a real capability.  So if 1.d is fixed by that,
> then something else is wrong.

Right, follow-on comments indicated it was a thinko on my part. I think
it make sense, based upon the context in the audit bug that perhaps we
just don't do auditing in unprivileged containers (similar to the 1.a

You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.

  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:

More information about the Ubuntu-server-bugs mailing list