3 ms·

Hype? Maybe 5 years ago, but nowadays? > I developed containers on windows and then I still had to debug the containers when deploying on Linux. There were for

Hype? Maybe 5 years ago, but nowadays? > I developed containers on windows and then I still had to debug the containers when deploying on Linux. There were formatting issues, filenotfound issues, and chmod issues You probably mean "building", not "deploying". If you've built it on windows, the container image will be the same on linux. > I have spent so much time configuring docker, and been able to complete the same task in a VM in a fraction of the time. Now imagine spending this time over and over and over again. > Am I doing it wrong? Is it the case that I am not the intended audience, and it's meant for larger teams? Have you been using tools like Vagrant or Ansimble? I think the most general mistake is using docker "as essentially VM", with typical VM workflows, instead of a build automation and distribution tool.

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 ago
  Depending 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.
kuramitropolis 4y ago
>If you've built it on windows, the container image will be the same on linux. If using Windows, issues with CRLF, case sensitivity, and file permissions, might occur as early as the build phase.

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 ago
Depending 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.

kuramitropolis 4y ago

>If you've built it on windows, the container image will be the same on linux. If using Windows, issues with CRLF, case sensitivity, and file permissions, might occur as early as the build phase.