4 ms·
One of the reasons that I prefer containers over VMs which rarely gets discussed is that Docker doesn't make me configure SSH, process managers, logging, monito
by throwaway894345 6y ago
One of the reasons that I prefer containers over VMs which rarely gets discussed is that Docker doesn't make me configure SSH, process managers, logging, monitoring, etc. Further, as much as I dislike the standard Docker image build tooling, it's generally much easier than building and managing VM images. I think AWS Fargate gets it pretty correct by using Firecracker to spin up distinct VMs for every Kubernetes pod or ECS task (basically units of 1+ collocated containers). I would like to see more support for this in Kubernetes offerings for bare metal and other cloud providers.
As an aside, there's also krustlet--an experimental project that uses Kubernetes to schedule WASM programs (instead of containers) which are less versatile but which are much lighter-weight and more secure than containers. I'm really excited for WASM orchestrators like this.
EDIT: Wow, I really didn't expect this to be controversial. I'm really curious about what people are objecting to with this?
- StreamBright 6y agoApples to oranges. Depends what do you want to manage in your infra. I also like to manage most of my infra so I usually use VMs, packaging (Packer) and custom deployment tools (Ansible) but for development workflows, tests, environment replication sometimes I use Docker. These are not interchangeable entirely.
- throwaway894345 6y agoFair enough. I was talking specifically about cloud environments. If you want to manage more things yourself, of course VMs are the way to go, but if you are looking to save yourself work I’m of the opinion that various container platforms are a very good option, not least of all because they let dev teams own more of the workload and thus less dependency on an ops team (and thus less coordination with the ops team, allowing the dev teams to move faster).