3 ms·
That sounds like a more heavyweight[0], and much more cumbersome[1] version of using Docker. [0] Much more CPU and RAM needed. [1] You rarely work with a fres
by davidatbu 4y ago
That sounds like a more heavyweight[0], and much more cumbersome[1] version of using Docker.
[0] Much more CPU and RAM needed.
[1] You rarely work with a fresh OS install; you'll have to install things, edit files in /etc/ or whatever, set firewall rules perhaps. For me at least, many of this comes with googling, say, "how do I allow an incoming TCP connection for a port range?". Ie, tiny details I don't want to memorize. I'll have to replicate these steps between the dev VM and the prod environment. If I use Docker, I can write these things into the Dockerfile and then just do "docker-compose up" in production, and it will just work. Also, I can commit that Dockerfile into a repo. It makes it much easier for others, or future-me, to understand what the dev-ops setup is like.