summaryrefslogtreecommitdiff
path: root/cmd/podman/varlink/io.podman.varlink
diff options
context:
space:
mode:
authorGiuseppe Scrivano <gscrivan@redhat.com>2019-03-19 12:08:52 +0100
committerGiuseppe Scrivano <gscrivan@redhat.com>2019-04-01 15:32:58 +0200
commit72382a12a7b5ac85e53474dfd6dcd83cd64a2738 (patch)
tree583f29064a2f11241895c23eabbd75cc1d5eb332 /cmd/podman/varlink/io.podman.varlink
parented326206f2b0ed80cdeddc63430bfbe60016c7df (diff)
downloadpodman-72382a12a7b5ac85e53474dfd6dcd83cd64a2738.tar.gz
podman-72382a12a7b5ac85e53474dfd6dcd83cd64a2738.tar.bz2
podman-72382a12a7b5ac85e53474dfd6dcd83cd64a2738.zip
rootless: use a single user namespace
simplify the rootless implementation to use a single user namespace for all the running containers. This makes the rootless implementation behave more like root Podman, where each container is created in the host environment. There are multiple advantages to it: 1) much simpler implementation as there is only one namespace to join. 2) we can join namespaces owned by different containers. 3) commands like ps won't be limited to what container they can access as previously we either had access to the storage from a new namespace or access to /proc when running from the host. 4) rootless varlink works. 5) there are only two ways to enter in a namespace, either by creating a new one if no containers are running or joining the existing one from any container. Containers created by older Podman versions must be restarted. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Diffstat (limited to 'cmd/podman/varlink/io.podman.varlink')
0 files changed, 0 insertions, 0 deletions