News for hackers. Stuff that matters.

A comment on How We Use Docker For Continuous Delivery – Part 2. Parent comment

Re:How We Use Docker For Continuous Delivery – Part 2 by fsaintjacques on Monday June 09, 2014 @01:17PM (#7869340)
Couldn't you just connect to the master host? I'm not sure how namespacing is done inside the kernel, but I would assume that the host would have access to containers info.
[ Parent | on HN ]
Re:How We Use Docker For Continuous Delivery – Part 2 by ah- on Monday June 09, 2014 @02:01PM (#7869588)
Yes, at least with raw lxc containers that's the case. You can simply see the processes in the container in the host top.
[ Parent | on HN ]
Re:How We Use Docker For Continuous Delivery – Part 2 by dorfsmay on Tuesday June 10, 2014 @12:30AM (#7871841)
Yes, you can, but then it means you need to keep track of which master your dockers are running on.
[ Parent | on HN ]
Re:How We Use Docker For Continuous Delivery – Part 2 by fsaintjacques on Tuesday June 10, 2014 @02:13PM (#7874324)
It's either tracking the slave you're on, or repackaging the whole linux userland in your container. I'd go for the first one.
[ Parent | on HN ]