3 ms·
How does this compare to vagrant?
by alexnewman 8y ago
How does this compare to vagrant?
- e1ven 8y agoOne big difference is that (afaik) people aren't putting vagrant images into production, it's for local development.
- alexnewman 8y agosure they do. you are totally wrong. they just shouldn’t
- cronix 8y agoDo people use vagrant in production?
- mikepurvis 8y agoOne hopes not, though they kinda do support it: https://www.vagrantup.com/docs/push/ https://www.vagrantup.com/docs/push/
- adrianmsmith 8y agoIn addition to the point others have raised that Vagrant is not designed to be used in production, Vagrant is a lot more stateful than Docker (long-lived VMs) so you can easily run “apt-get update && apt-get upgrade” or equivalent. Potentially from the Vagrantfile to make sure rebuilds get the updates as well.
- alexnewman 8y agoyou are totally wrong i know plenty of people who do. i also know people who think docker shouldn’t be used in production and that we should use containerd just like vagrant/packer
- fulafel 8y agoIt's kind of apples and oranges. Vagrant can used different container and vm runtimes as the runtime ("provider" in vagrant language). It's a configuration engine. So there is no single image format for Vagrant, and you might use kvm or LXD or VMware or Docker as your Vagrant provider.
- alexnewman 8y agosame with containers. plenty of backends