3 ms·
Docker truthfully told is unusable for Dev envs that need to change constantly. It was never built to handle this use case. I haven't seen a good docker compose
by aszen 5y ago
Docker truthfully told is unusable for Dev envs that need to change constantly. It was never built to handle this use case.
I haven't seen a good docker compose file that can be reliably used as a development environment in multiple oses with good performance. There's all sorts of edge cases where volumes don't work.
In my opinion docker is very useful for thing like dbs, queues and other processes where the underlying code doesn't change.
But for everyday frontends and backends it's not worth it.
Nowadays I write a shell.nix file which contains all the dependencies the project needs, it works but is definitely not as easy to learn as a docker file
- okamiueru 5y agoOut of curiosity, what OS are you on?
- aszen 5y agoI'm on Linux, but still things aren't all rosy.
- mike_d 5y agoDev should look just like production if you are doing it right, and you are correct dev was basically an afterthought in Docker. If you run this in a screen session it will auto rebuild as you make changes, which is the closest I've been able to come to containerizing my development style: https://gist.github.com/mikedamm/53dc6a78b976eeac88893427424c2527 https://gist.github.com/mikedamm/53dc6a78b976eeac88893427424...
- aszen 5y agoWhen people say docker helps in making dev look like prod, I assume they are running everything on docker in production, but that is very rarely the case with dbs, queues and cloud specific services. Interesting I'll check this script, but I have doubts doing a rebuild is going to be quick enough even with good cache layering in the Dockerfile. Use case is that I have frontend and backend code in one repo, and make changes across them that need to be reflected in the ui.