How Container Filesystem Works: Building a Docker-Like Container from Scratch
1–10 of 34 posts
Re: How Container Filesystem Works: Building a Docker-Like Container from Scratch
#2Re: How Container Filesystem Works: Building a Docker-Like Container from Scratch
#3We had chroot since 1979, nobody managed to build a docker like wrapper for chroot which do not require netns?
Re: How Container Filesystem Works: Building a Docker-Like Container from Scratch
#4We had chroot since 1979, nobody managed to build a docker like wrapper for chroot which do not require netns?
Much of the technology was there, but Docker was able to achieve a critical mass, with streamlined workflows. Perhaps as much a social phenomenon as a technical one?
Re: How Container Filesystem Works: Building a Docker-Like Container from Scratch
#5We had chroot since 1979, nobody managed to build a docker like wrapper for chroot which do not require netns?
Docker is more than just chroot. You also need: overlay file system; OCI registry and community behind it, to create thousands of useful images. And, of course, the whole idea of creating images layer by layer and using immutable images to spawn mutable containers.
I don't actually think that you need network or process isolation. In terms of isolation, chroot is enough for most practical needs. Network and process isolations are nice to have, but they are not essential.
Re: How Container Filesystem Works: Building a Docker-Like Container from Scratch
#6We had chroot since 1979, nobody managed to build a docker like wrapper for chroot which do not require netns?
FreeBSD has had jails since version 4 (~year 2000), fwiw. Much of the technology was there, but Docker was able to achieve a critical mass, with streamlined workflows. Perhaps as much a social phenomenon as a technical one?
Re: How Container Filesystem Works: Building a Docker-Like Container from Scratch
#7We had chroot since 1979, nobody managed to build a docker like wrapper for chroot which do not require netns?
Docker is a genius idea which looks obvious in retrospect, but someone need to invent it. Docker is more than just chroot. You also need: overlay file system; OCI registry and community behind it, to create thousands of useful images. And, of course, the whole idea of creating images layer by layer and using immutable images to spawn mutable containers. I don't actually think that you need network or process isolatio…
process isolation is less prominent
Re: How Container Filesystem Works: Building a Docker-Like Container from Scratch
#8Earlier quoted context omitted.
FreeBSD has had jails since version 4 (~year 2000), fwiw. Much of the technology was there, but Docker was able to achieve a critical mass, with streamlined workflows. Perhaps as much a social phenomenon as a technical one?
I think the real genius of Docker was the image packaging. The pieces were there but delivery and scripting it all wasn't easy.
They're way closer to the usual "Unix" tool feel too. Docker feels 100% like an attempt to get rich by engineering a monolith rather than be a few helper C tools. Docker was so annoying to learn.
Fortunately with the end of ZIRP and SaaS deflation (in real user terms, not fake investment to project we still live in the 2010s heyday), software engineers are focused on engineering more than hype generation. Am excited about energy based models, capture of electromagnetic geometry of the machine as it runs programs.
60s style lexical state management systems dragged forward in time because of social momentum have little to do with engineering. Are hardly high tech in 2025.
Re: How Container Filesystem Works: Building a Docker-Like Container from Scratch
#9We had chroot since 1979, nobody managed to build a docker like wrapper for chroot which do not require netns?
Re: How Container Filesystem Works: Building a Docker-Like Container from Scratch
#10We had chroot since 1979, nobody managed to build a docker like wrapper for chroot which do not require netns?
FreeBSD has had jails since version 4 (~year 2000), fwiw. Much of the technology was there, but Docker was able to achieve a critical mass, with streamlined workflows. Perhaps as much a social phenomenon as a technical one?
The effort to introduce the concepts to the mainstream can’t be understated. It seems mundane now but it took a lot of grassroots effort and marketing to hit that critical mass.