Re:Don't expose the docker socket, even to a container
by davexunit on Thursday September 24, 2015 @10:11AM
(#10271661)
Yes, this is a fundamental issue with Docker and other container systems that work with raw disk images as their basic unit of information. I have implemented a container system for the GNU Guix package manager that doesn't have this image bloat problem because it doesn't use opaque disk images. We store packages in a content-addressable storage system, which allows us to know the precise dependency graph for any piece of software in the system. Since we know the full set of software needed for any container, we are able to share the same binaries amongst all containers on a single host via a bind mount.
[ Parent
| on HN ]
There are no comments on this comment yet.