this post was submitted on 21 Jul 2023
86 points (93.0% liked)
Programming
17424 readers
25 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If your dev documentation includes your devs running
docker build, you're doing docker wrong.The whole point is that you can build a working container image and then ship it to a registry (including private registries) so that your other developers/users/etc don't have to build them and can just run the existing image.
Then for development, you simply use a bind mount to ensure your local copy of the code is available in the container instead of the copy the container was built with.
That doesn't solve the performance issues on Windows and Mac, but it does prevent the "my environment is broke" issues that docker is designed to solve
Agreed, we still do this in the areas where we use Docker at day job.
I think the mileage with this approach can vary depending on the languages in use and the velocity of feature iteration (ie. if the company is still tweaking product-market fit, pivoting to a new vertical, etc.).
I've lost count of the number of times where a team decides they need to
npm installsomething with a heavynode-gypstep to build native modules which require yet another obscure system dependency that is not in the base layer. 😅