Comment by hintymad 3 days ago
Honest question: why do people prefer developing code inside a docker? I get the benefits of docker as a deployment unit, but wouldn’t configuring a dev container and using it a hassle nonetheless, compared to not doing them at all?
If you commit the .devcontainer.json and associated files your whole team gets a consistent, local-feeling, environment for free.
Containerisation solved the "Works on my machine" gap between local and prod. This is just solving for the same gap between Dev 1 and Dev 2.
That's a different thing. You're talking about running the software under development in a container. I think the commenter was asking about running the dev tooling in a container, which I find a massive pain.
Devcontainers don't "feel" local to me, since my CLI tools are not available in them. Think ripgrep or fd, for example.
You could include those as part of the tooling. I have been experimenting with including mise as part of the image and then layer on the extra tools within there. Put all of those steps into the build so it is automatic.
Separation of dependencies and ability to easily interconnect containers.
If you’re like me and want to maintain a clean dev machine. I don’t want my machine to get in my way when I need to get work done. That means I don’t want some X messing things up somewhere that I didn’t know about. Older I get my memory isn’t as sharp and things like this matter.
Personally I don’t trust running npm/pip/gradle/etc in my own machine. I feel more secure running them in containers or VMs. Some IDEs like jetbrains’ support remote development (it’s not perfect but better than risking my own machine)