Alexander LarssonandVictor Vieux 40ab3d4138 lxc: Work around lxc-start need for private mounts ...

lxc-start requires / to be mounted private, otherwise the changes
it does inside the container (both mounts and unmounts) will propagate
out to the host.

We work around this by starting up lxc-start in its own namespace where
we set / to rprivate.

Unfortunately go can't really execute any code between clone and exec,
so we can't do this in a nice way. Instead we have a horrible hack that
use the unshare command, the shell and the mount command...
Upstream-commit: e40f5c7cb90fbc719241ace45b05c2c61aced658
Component: engine

2013-09-26 15:09:32 +00:00

components/engine

lxc: Work around lxc-start need for private mounts

2013-09-26 15:09:32 +00:00

S

Description

The Docker CLI

clidocker

358 MiB

Languages

Go 92.3%

Shell 5.4%

Dockerfile 1.1%

Go-Checksums 0.7%

Makefile 0.3%

Other 0.2%