Re:Tiny Linux distro that runs the entire OS as Docker conta...
by dozzie on Sunday April 30, 2017 @07:33AM
(#14231070)
> Just google "doesn't work in chroot" and you'll be reminded of a litany of issues that come up when trying to build/run things in a chroot
Yeah, some newbie forgot to mount-bind a necessary directory like /proc or /dev, didn't provide sensible /etc/resolv.conf, or messed up host's and chroot's paths, either in request or in configuration. Nothing that would render chroot unviable. Is this what you meant?
Re:Tiny Linux distro that runs the entire OS as Docker conta...
by jstarks on Sunday April 30, 2017 @05:49PM
(#14234035)
Why would anyone want to get all that right manually when containers manage all that automatically?
Re:Tiny Linux distro that runs the entire OS as Docker conta...
by dozzie on Monday May 01, 2017 @07:40AM
(#14236846)
Good question. Why anyone presented with fancy and fashionable third party
software would use a mechanism that has been present for decades, ships with
the operating system, works reliably and predictably, doesn't change
substantially every quarter, doesn't do any magical things to network
configuration, and is easy to inspect, debug, and adjust for an outsider? Why
indeed?
And I'm not confusing containers and Docker, I'm just speaking a bit imprecisely. In my experience, conversations about "containers" are rarely about raw containers, but rather some specific containerization scheme and tools (e.g. docker). I suspect everyone in this entire subthread means "docker containers" when they says "containers."