We tried to fix the systemd stuff with the shared mounts in 2698c20ae42860b10b21174a2c67db2e1d0ecc29 and 7c2397d7c11185680b167fbb0e8bbfb62cb338ca, broke vmount (mount from the admin namespace), reverted the commit in 56d2df4f2a4d47471bda42c42d11ce4564937d69 and broke support with systemd on the host.
After reading the documentation about shared subtrees I am pretty sure, that we do not want to have private mounts but slave mounts. That way the mounts from parent namespaces could propagate into the vserver, but the changes made while starting the container does not propagate up to the host.
We tried to fix the systemd stuff with the shared mounts in 2698c20ae42860b10b21174a2c67db2e1d0ecc29 and 7c2397d7c11185680b167fbb0e8bbfb62cb338ca, broke vmount (mount from the admin namespace), reverted the commit in 56d2df4f2a4d47471bda42c42d11ce4564937d69 and broke support with systemd on the host.
After reading the documentation about shared subtrees I am pretty sure, that we do not want to have private mounts but slave mounts. That way the mounts from parent namespaces could propagate into the vserver, but the changes made while starting the container does not propagate up to the host.