>> 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:
>
> 999-cpc-fixes.chroot:
> ## --------------
> # for maverick and newer, use LABEL= for the '/' entry in fstab
> if [ -n "${root_fs_label}" ]; then
> bl="[:blank:]"
> lstr="LABEL=${root_fs_label}"
> sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1,"
> "${rootd}/etc/fstab"
> fi
> cat > /etc/fstab << EOM
> LABEL=cloudimg-rootfs / ext4 defaults 0 0
> EOM
I think the cleanest solution would be providing images for containers without
this invalid fstab entry.
The second cleanest seems to be not starting systemd-remount-fs.service in
containers, or at least not in lxc.
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
