2 ms·
A few jobs back, I managed to replace hundreds of lines of Vagrant configuration with a tiny docker file. On the other hand, I've also had the misfortune of ta
by zdragnar 4y ago
A few jobs back, I managed to replace hundreds of lines of Vagrant configuration with a tiny docker file.
On the other hand, I've also had the misfortune of taking over a project where the previous developers' docker / compose made some use of `docker.for.mac.host.internal` and I was running docker on linux. At the time, there wasn't linux support for `docker.host.internal` and, to confuse matters, running rootless vs as root behaved differently as well. At this point in time my docker experience was pretty limited, so I had to give myself a rough crash course in docker and linux networking.
- danwee 4y agoDepending on the configuration, sometimes you cannot just replace a Vagrant setup with Docker. In my experience Vagrant VMs are used to reproduce cloud environments locally. For instance if you want to run locally "an ubuntu server running systemd plus sshd", you cannot just use Docker for that (well, I bet you can make Docker run systemd and other things, but that's not the intention of the tool), you have to use a VM. Now, sure if you are using a VM to run your Node application, well, you can easily use Docker instead.