runc/libcontainer/system
Serge Hallyn c0ad40c5e6 Do not create devices when in user namespace
When we launch a container in a new user namespace, we cannot create
devices, so we bind mount the host's devices into place instead.

If we are running in a user namespace (i.e. nested in a container),
then we need to do the same thing.  Add a function to detect that
and check for it before doing mknod.

Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
---
 Changelog - add a comment clarifying what's going on with the
	     uidmap file.
2016-01-08 12:54:08 -08:00
..
linux.go Do not create devices when in user namespace 2016-01-08 12:54:08 -08:00
proc.go Move libcontainer into subdirectory 2015-06-21 19:29:15 -07:00
setns_linux.go Move libcontainer into subdirectory 2015-06-21 19:29:15 -07:00
syscall_linux_64.go Move libcontainer into subdirectory 2015-06-21 19:29:15 -07:00
syscall_linux_386.go Fix build tags 2015-07-01 13:22:09 -07:00
syscall_linux_arm.go Fix build tags 2015-07-01 13:22:09 -07:00
sysconfig.go Move libcontainer into subdirectory 2015-06-21 19:29:15 -07:00
sysconfig_notcgo.go Move libcontainer into subdirectory 2015-06-21 19:29:15 -07:00
xattrs_linux.go Move libcontainer into subdirectory 2015-06-21 19:29:15 -07:00