3 ms·
I think this view of Docker is pretty common: poor man's virtualization. You'd prefer real VMs but you can't reliably & performantly run nested VMs on public pr
by fulafel 9y ago
I think this view of Docker is pretty common: poor man's virtualization. You'd prefer real VMs but you can't reliably & performantly run nested VMs on public providers. Or can you? What's the current status on AWS/GCP/DigitalOcean/Hetzner?
- chubot 9y ago(tangent here) I didn't get that from the article. He said that the tooling around Docker is clunky: But I’ve always felt a bit like the Dockerfile you write is hard to maintain. I have to use some Makefile trickery to prevent having to repeat parts of the Dockerfile amongst each of the containers. I don't like Docker either, but it's not because I want VMs. I want VMs even less than I want Docker! I want containers that are fast and light. Basically I want to solve the problems of reproducibility/stability/portability with as little code as possible. VMs a bad way to do that because they involve not just a new user space like Docker, but a new kernel and hypervisor too!