I noticed in some CentOS 7 containers an init boot failure with systemd-remount-fs.service. Not fatal but I traced the cause to /etc/fstab, which contains the following:
When logging into the CentOS container, /dev/root does not exist. Commenting out that entry in fstab resolves the init boot failures.
1. Is the /etc/fstab entry still valid or is this from an old CentOS template?
2. My understanding is I should be able to view the file system of a container from the Proxmox host at /var/lib/lxc/$cid/rootfs. Yet there is nothing in that directory. If possible how do I enable that feature?
I looked in the wiki and admin manual but I am not seeing how to do this.
In /etc/pve/lxc/$cid.conf I see entries like this:
rootfs: local-lvm:vm-$cid-disk-1,size=120G
In /var/lib/lxc/$cid/config I see entries like this:
lxc.rootfs.path = /var/lib/lxc/$cid/rootfs
I seem to recall earlier versions (3.x?, 4.x?) of Proxmox populating the rootfs directory. The containers have been in service since then. Perhaps with subsequent Proxmox releases I need to tweak the configs?
Code:
/dev/root / rootfs defaults 0 0
When logging into the CentOS container, /dev/root does not exist. Commenting out that entry in fstab resolves the init boot failures.
1. Is the /etc/fstab entry still valid or is this from an old CentOS template?
2. My understanding is I should be able to view the file system of a container from the Proxmox host at /var/lib/lxc/$cid/rootfs. Yet there is nothing in that directory. If possible how do I enable that feature?
I looked in the wiki and admin manual but I am not seeing how to do this.
In /etc/pve/lxc/$cid.conf I see entries like this:
rootfs: local-lvm:vm-$cid-disk-1,size=120G
In /var/lib/lxc/$cid/config I see entries like this:
lxc.rootfs.path = /var/lib/lxc/$cid/rootfs
I seem to recall earlier versions (3.x?, 4.x?) of Proxmox populating the rootfs directory. The containers have been in service since then. Perhaps with subsequent Proxmox releases I need to tweak the configs?