3 ms·
A couple of awkward things with docker: * Each container is kept indefinitely and it's up to the user to adopt a garbage-collection strategy. * Images built w
by zimbatm 13y ago
A couple of awkward things with docker:
* Each container is kept indefinitely and it's up to the user to adopt a garbage-collection strategy.
* Images built with a Dockerfile contain the build dependencies even if they're not needed at runtime. That has to be a better way.
* Docker is still single-host. If you want to scale horizontally you need to build another layer on to to run the containers on different machines. But then features like container links don't work anymore.
* Unlike the real physical container it actually matters what's inside the box. You can't run the same container on different CPU architectures.
- joevandyk 13y agoI think recent versions of Docker fixed the GC problem: https://github.com/dotcloud/docker/issues/928#issuecomment-28249901 https://github.com/dotcloud/docker/issues/928#issuecomment-2... and https://github.com/dotcloud/docker/pull/1589 https://github.com/dotcloud/docker/pull/1589 If you didn't want the build deps, you could create a Dockerfile for building the binaries, then another one for copying them to the release container.
- SEJeff 13y agoCoreOS + etcd... Nuff said! [1] http://coreos.com http://coreos.com [2] http://coreos.com/using-coreos/etcd/ http://coreos.com/using-coreos/etcd/