4 ms·

Because you have a clean start every-time you do something. When you use a machine on a daily basis you will have lots of your own scripts, software etc that wi

by davesmith1983 7y ago

Because you have a clean start every-time you do something. When you use a machine on a daily basis you will have lots of your own scripts, software etc that will be in your path. A lot of times issues occur between machines because your build your instructions or your build scripts whatever have something that is specific to your machine / user account whatever that someone else might not have. If you use VM you will know that whatever the default VM is in vagrant that you tell them to use will be the same. It isn't always necessary but tbh I am not in the habit of doing it.

jnurmine 7y ago
But still, why VMs? A container seems even better suited for this purpose, since the only thing really required for this use-case is a certain configuration of system software as well as a separation from the rest of the system. Lxc/lxd can do it, Docker can do it, et cetera, the actual technology does not matter. As a plus, builds will be faster vs. a VM.
- fredthomsen 7y ago
  Have to agree. This has been my main workflow for the past year and a half and the speed increase alone makes it worth it
- davesmith1983 7y ago
  Containers weren't a thing back in 2014. Vagrant IIRC was fairly new and I remember sitting next to a guy that was scripting much of this up.
  - zokier 7y ago
    Containers were definitely a thing in 2014; Docker was getting hyped, LXC got 1.0 release after 5 years of developement, and people had been using stuff like OpenVZ long before. May 19, 2013 Docker - Way better than a VM https://news.ycombinator.com/item?id=5731706 https://news.ycombinator.com/item?id=5731706
    - davesmith1983 7y ago
      Well what is hyped up on hackernews might see the inside of corporate office in maybe another 10 years time.
  - ciupicri 7y ago
    But chroot was a thing back in 2014. Fedora's mock used chroot for building RPMs from source RPMs [1]. [1]: https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds#What_is_Mock.3F https://fedoraproject.org/wiki/Using_Mock_to_test_package_bu...

jnurmine 7y ago

But still, why VMs? A container seems even better suited for this purpose, since the only thing really required for this use-case is a certain configuration of system software as well as a separation from the rest of the system. Lxc/lxd can do it, Docker can do it, et cetera, the actual technology does not matter. As a plus, builds will be faster vs. a VM.

fredthomsen 7y ago
Have to agree. This has been my main workflow for the past year and a half and the speed increase alone makes it worth it
davesmith1983 7y ago
Containers weren't a thing back in 2014. Vagrant IIRC was fairly new and I remember sitting next to a guy that was scripting much of this up.
- zokier 7y ago
  Containers were definitely a thing in 2014; Docker was getting hyped, LXC got 1.0 release after 5 years of developement, and people had been using stuff like OpenVZ long before. May 19, 2013 Docker - Way better than a VM https://news.ycombinator.com/item?id=5731706 https://news.ycombinator.com/item?id=5731706
  - davesmith1983 7y ago
    Well what is hyped up on hackernews might see the inside of corporate office in maybe another 10 years time.
- ciupicri 7y ago
  But chroot was a thing back in 2014. Fedora's mock used chroot for building RPMs from source RPMs [1]. [1]: https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds#What_is_Mock.3F https://fedoraproject.org/wiki/Using_Mock_to_test_package_bu...