4 ms·
"dockerized insanity" made me chuckle. usually docker has resulted in a lot less debugging "works on my machine" issues, because unless you have patched your k
by sascha_sl 5y ago
"dockerized insanity" made me chuckle.
usually docker has resulted in a lot less debugging "works on my machine" issues, because unless you have patched your kernel in a really messy way it is impossible to not reproduce issues when testing in docker.
hell, I moved a startup-ish company single handedly from uploading PHP scripts to a "development server" (VM on a scuffy proxmox box in the closet) where they didn't even know if all the code was current and constantly stepped on each other's toes to a docker-compose.yaml, a Dockerfile and an A4 cheat sheet on how to use it (including resetting the database and such) in a week or so. it's an amazing tool to ensure consistency.
- Joeri 5y agoDon't get me wrong. I deploy all my API's in docker containers as well, for similar reasons. But I do feel like a victim of stockholm syndrome whenever I think of docker as a solution instead of a workaround for problems self-imposed by our byzantine development tooling stacks. It is now even starting to make sense to run the entire suite of tools for local web development inside of a local docker container, because of the risk of subtle conflicts in devDependencies between machines. At what point are we going to concede this way of building software is madness? How many layers are too many layers?