gvisor/runsc
Andrei Vagin a46b6d453d runsc: set up a minimal chroot from the sandbox process
In this case, new mounts are not created in the host mount namspaces, so
tearDownChroot isn't needed, because chroot will be destroyed with a
sandbox mount namespace.

In additional, pivot_root can't be called instead of chroot.

PiperOrigin-RevId: 229250871
Change-Id: I765bdb587d0b8287a6a8efda8747639d37c7e7b6
2019-01-14 14:08:19 -08:00
..
boot Automated rollback of changelist 225089593 2019-01-02 15:48:00 -08:00
cgroup Restore to original cgroup after sandbox and gofer processes are created 2019-01-09 09:18:15 -08:00
cmd runsc: set up a minimal chroot from the sandbox process 2019-01-14 14:08:19 -08:00
console Track paths and provide a rename hook. 2018-10-23 00:20:15 -07:00
container runsc: Collect zombies of sandbox and gofer processes 2019-01-11 10:32:26 -08:00
fsgofer Undo changes in case of failure to create file/dir/symlink 2019-01-07 23:02:19 -08:00
sandbox runsc: set up a minimal chroot from the sandbox process 2019-01-14 14:08:19 -08:00
specutils Restore to original cgroup after sandbox and gofer processes are created 2019-01-09 09:18:15 -08:00
test runsc: set up a minimal chroot from the sandbox process 2019-01-14 14:08:19 -08:00
tools/dockercfg Internal change. 2018-11-28 14:01:48 -08:00
BUILD runsc: Pass log and config files to sandbox process by FD. 2018-09-04 20:10:01 -07:00
main.go Automated rollback of changelist 225089593 2019-01-02 15:48:00 -08:00