3 ms·
Not sure I get the last point. Spawning a shell in a container, persisting the changes made and distributing such edited container is trivial. Of course once yo
by seba_dos1 3y ago
Not sure I get the last point. Spawning a shell in a container, persisting the changes made and distributing such edited container is trivial. Of course once you want to rebuild it reproducibly from scratch you need to edit the Dockerfile, but then it's exactly the same in Vagrant, isn't it?
Perhaps the difference is that storing your changes is an explicit operation that needs to happen consciously, and that data is usually persisted outside of the container.
- pmontra 3y agoThe scenario is: write a Vagrantfile and create the VM on Linux, then manually fix it or evolve it and never destroy and rebuild the VM. Then give that Vagrantfile to somebody on Windows a couple of years later. Chanches are that it won't work as intended. That's more difficult to happen with a container and its image.