Comment 30 for bug 1576341

On 08.05.2017 [11:25:03 -0000], Balint Reczey wrote:
> >> 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.

I *think* containers and VMs use the same cloud image, so I don't think
bifurcating for this one change is reasonable.

> The second cleanest seems to be not starting
> systemd-remount-fs.service in containers, or at least not in lxc.

Except it's possible that a user might have other entries that should be
remounted, possibly? When, say, passing real disks into the container?