I am mounting /dev/shm manually via profile with:
raw.lxc: lxc.mount.entry = none dev/shm tmpfs rw,nosuid,nodev,noexec,create=dir
as a workaround inside containers, because /etc/init.d/devfs is -lxc keyworded.
When removing the -lxc I can boot the container without any issues and also the /dev/shm gets mounted correctly. I don't know what is the reason not to run devfs inside container. Can this be considered and possibly fixed?
There is no difference between mounts in a container using profile and container using modified devfs with removed -lxc keyword.
Thank you
I am mounting /dev/shm manually via profile with:
raw.lxc: lxc.mount.entry = none dev/shm tmpfs rw,nosuid,nodev,noexec,create=diras a workaround inside containers, because /etc/init.d/devfs is -lxc keyworded.
When removing the
-lxcI can boot the container without any issues and also the /dev/shm gets mounted correctly. I don't know what is the reason not to run devfs inside container. Can this be considered and possibly fixed?There is no difference between mounts in a container using profile and container using modified devfs with removed -lxc keyword.
Thank you