Hacker News new | past | comments | ask | show | jobs | submit login

I'm still missing a piece of the puzzle. With Vagrant, though heavy weight, I have a completely defined system. If I spin up my production server using the same definition (I use ansible) as my Vagrant config, I guarantee the same outcome. Seems perfect. With Docker, since it relies on the underlying os, it seems I could run into compatibility problems. I understand the "lightweight" aspect, but if I have compatibility problems, that seems not worth the benefit. OR is the issue that those compatibility problems are illusory - Ubuntu 11 will be the same as Ubuntu 12 and CoreOs xx and LinuxZ ZZ? With Docker, what do I lose vs. Vagrant and what do I gain that makes that worthwhile?



with docker, your guest machines run the same kernel as your host, but a different root filesystem and init system. the result is that you can run centOS on docker on Ubuntu, but you'll get centOS with the Ubuntu kernel. So, you lose some flexibility with the kernel of your VM. But a docker container is extremely light weight. it boots in a few hundred milliseconds, and it only costs a small amount more resources to run a service inside docker than if you had just run the service on the host system directly.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: