Re:Lmctfy: Google's Linux application container stack
by shykes on Thursday October 03, 2013 @03:22AM
(#6487586)
Damn. This means it's much less useful to me (and 99% of applications outside of google). I guess I could combine lmctfy with a namespacing library of my own. But that's more extra work than I was anticipating.
Re:Lmctfy: Google's Linux application container stack
by thockin on Thursday October 03, 2013 @03:30AM
(#6487609)
Namespaces will be coming, but we're not there yet. This captures some of what we are already doing internally, but not all of it, yet.
Re:Lmctfy: Google's Linux application container stack
by SEJeff on Thursday October 03, 2013 @08:52PM
(#6493120)
Perhaps they'd be open to a collaboration where you add that functionality and then you use it to make docker (even more!) awesome.
Re:Lmctfy: Google's Linux application container stack
by justincormack on Thursday October 03, 2013 @04:46PM
(#6491910)
The namespacing part is much simpler, if you have specific use cases.
And you can approximate mount namespaces with chroots and bind mounts. (In some ways that's better, since it's a bit easier for a process outside the container to interact with the container's filesystem).