>> 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.
>> 1.b i'd like another way to do that, but not sure what a better way would fixes.chroot: ${root_ fs_label} " ${bl}]* \([${bl} ]*/[${bl} ].*\),$ {lstr}\ 1," "${rootd} /etc/fstab" rootfs / ext4 defaults 0 0
>> be.
>
> Yeah, I spent some time looking at the CPC generater and it seems like
> this is pretty hard-coded:
>
> 999-cpc-
> ## --------------
> # for maverick and newer, use LABEL= for the '/' entry in fstab
> if [ -n "${root_fs_label}" ]; then
> bl="[:blank:]"
> lstr="LABEL=
> sed -i "s,^[^#
> fi
> cat > /etc/fstab << EOM
> LABEL=cloudimg-
> EOM
I think the cleanest solution would be providing images for containers without this invalid fstab entry. remount- fs.service in containers, or at least not in lxc.
The second cleanest seems to be not starting systemd-