3 ms·
I might be wrong, but I think his point is that by the time you're running a linux VM for docker, why not go ahead and get the rest of the tooling for free? Do
by horsawlarway 5y ago
I might be wrong, but I think his point is that by the time you're running a linux VM for docker, why not go ahead and get the rest of the tooling for free?
Docker can still be run in the VM just fine, for cases where you want a reproducible build environment.
I do this at any company that lets me (and by lets, I mean doesn't explicitly forbid) - They all give me a Mac, and the first (and sometimes only) thing I install is usually vmware fusion, followed by the linux distro of my choice (Arch).
- SkyMarshal 5y ago>for cases where you want a reproducible build environment. Or just create your reproducible build environment as a QEMU VM image instead of a docker file. That way you only have to install a VM image, instead of install VM image/OS + install Docker + install your Docker file.
- dolmen 5y agoJust the cost of porting one single Dockerfile to anything else is bigger than the Docker licence cost for 1 year.
- horsawlarway 5y agoSee, I don't really agree here. Containers solve a different problem than vms. The biggest issues (at least for me) are 1. The second a dev starts using that VM, it's no longer reproducible. The goal of docker is that a developer can create reproducible images as a part of normal development. 2. I won't be running that QEMU vm in production, but I might very well be running the exact same container image in both development and production.