> The whole point of Docker containers is that they're very efficient with their resource and space usage. If you have 15 redundant frameworks pre-loaded in a container, of which you use at most 3, you're using Docker wrong.
It is true that Docker is more space efficient than setting up whole VMs for each app. But it's a lot less space efficient than installing everything on a big server. If you are running, say, a bunch of Python apps, the lowest-space approach is making sure they all use the same set of libraries, modules, and other required resources. But harmonizing those versions is a pain in the ass, so Docker lets you easily use multiple copies of python, overlapping libraries, python packages, etc.
It's true that if you were deploying this in production, you'd want to trim this back. But this is explicitly a "research environment".
Absolutely loading loads of packages in a container is never a good idea for production. But Deepo is not for production, it is a playground. It is a thing which help people to explore and learn these packages without a hassle and the worry for messing up their system.
Indeed, having played around dl-docker, I really appreciate the author of Deepo. It seems like to be more updated, more well-covered, and more promising to me.
The larger you get, the higher the chance that dependency hell will cripple the velocity of a project.
Docker helps a ton in these types of scenarios.
No, that's http://flatpak.org/
Good to see the hacker spirit is alive and well here.
We have a 9GB+ docker image that we create containers from some 10k times per day for our users in production.
Would be interesting to hear about what your use case is, and how it works for you.
Here is one of our high-traffic product: https://codepad.remoteinterview.io/
It's used by interviewers, students, teachers who need a quick place to practice and pair-program.
Why take the effort to get the kids to play nice with each other when you can lock each of them in their own room?
Overlay was started and quickly abandoned. Only to be replaced by overlay2 that is work in progress and not wildly available yet.
This article contains a bit of history on Docker filesystems: https://thehftguy.com/2016/11/01/docker-in-production-an-his...