moby--moby/pkg/chrootarchive
Serge Hallyn 617c352e92 Don't create devices if in a user namespace
If we are running in a user namespace, don't try to mknod as
it won't be allowed.  libcontainer will bind-mount the host's
devices over files in the container anyway, so it's not needed.

The chrootarchive package does a chroot (without mounting /proc) before
its work, so we cannot check /proc/self/uid_map when we need to.  So
compute it in advance and pass it along with the tar options.

Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
2016-08-12 16:26:58 -04:00
..
archive.go Correct build-time directory creation with user namespaced daemon 2015-10-20 08:59:48 -04:00
archive_test.go Windows CI: Unit Tests stop running failing chrootarchive tests 2016-03-01 14:28:29 -08:00
archive_unix.go Fix docker import tests 2016-05-23 15:34:40 -07:00
archive_windows.go Windows: Fix long path handling for docker build 2015-09-15 10:58:11 -07:00
chroot_linux.go pkg: chrootarchive: chroot_linux: fix mount leak 2016-06-11 00:07:41 +02:00
chroot_unix.go Use pivot_root instead of chroot for chrootarchive 2016-05-04 19:55:34 -04:00
diff.go Add user namespace (mapping) support to the Docker engine 2015-10-09 17:47:37 -04:00
diff_unix.go Don't create devices if in a user namespace 2016-08-12 16:26:58 -04:00
diff_windows.go Add user namespace (mapping) support to the Docker engine 2015-10-09 17:47:37 -04:00
init_unix.go Remove flush(stdout) in pkg/chrootarchive/diff_unix.go and improve error reporting of flush() to fix #21103 2016-03-15 10:29:51 -07:00
init_windows.go Windows: Docker build starting to work 2015-06-17 10:41:28 -07:00