Michael Crosby 0dcae82acb Initially mount /sys as ro instead of remount ...

The issue with doing a remount as ro with sysfs is that if a container
is still in one of the hosts namepsaces, commonly with the NET
namespace, the remount will cause the host's systems sysfs to be
remounted as ro also.  We can fix this correctly by not doing the
remount and just mount sys as ro in the first place.

The other remounts are individual files within proc so they will not
have this issue.

For context please see:
https://github.com/dotcloud/docker/issues/7101
Docker-DCO-1.1-Signed-off-by: Michael Crosby <michael@docker.com> (github: crosbymichael)

2014-07-18 14:13:38 -07:00

..

create.go

Rename Container -> Config.

2014-06-23 17:08:15 -07:00

exec.go

Don't open slave in parent

2014-07-15 18:24:15 -07:00

execin.go

Add initial system pkg to libcontainer

2014-07-14 16:46:51 -07:00

init.go

Initially mount /sys as ro instead of remount

2014-07-18 14:13:38 -07:00

nsenter.go

Add option parsing to nsenter and enable specifying commands with arguments.

2014-06-18 14:29:40 -04:00

types_linux.go

Updated libcontainer subpackage dependencies. Most subpackages now do not depend on their parent ('libcontainer') package. 'namespaces' and 'nsinit' still do.

2014-06-20 22:52:43 +00:00

types_test.go

Updated libcontainer subpackage dependencies. Most subpackages now do not depend on their parent ('libcontainer') package. 'namespaces' and 'nsinit' still do.

2014-06-20 22:52:43 +00:00

types.go

Updated libcontainer subpackage dependencies. Most subpackages now do not depend on their parent ('libcontainer') package. 'namespaces' and 'nsinit' still do.

2014-06-20 22:52:43 +00:00