Why do I not see linux name spaces for my warden instances?

root(a)874c4cea-19ed-41c7-abd2-09eb5851d54d:/var/vcap/data/warden/depot# ip netns list <-- note that the output was blank
root(a)874c4cea-19ed-41c7-abd2-09eb5851d54d:/var/vcap/data/warden/depot# ls
19b0ug03pal 19b0ug03pba tmp <-- however, there are two containers up and running

Warden does not create a bind mount to the network namespace. If you want
to find the namespace, locate the pid of the wshd associated with the
container and use /proc/${pid}/ns/net as the namespace.

`ip netns` only references bind mounts in /var/run/netns; I don't know of
any container systems that actually use that default location.

On Wed, Mar 23, 2016 at 4:27 PM, ravi malhotra <ravi.malhotra(a)bnymellon.com>
wrote:

Why do I not see linux name spaces for my warden instances?

root(a)874c4cea-19ed-41c7-abd2-09eb5851d54d:/var/vcap/data/warden/depot# ip
netns list <-- note that the output was blank
root(a)874c4cea-19ed-41c7-abd2-09eb5851d54d:/var/vcap/data/warden/depot# ls
19b0ug03pal 19b0ug03pba tmp <-- however, there are two containers up and
running

--
Matthew Sykes
matthew.sykes(a)gmail.com