4 ms·
TL;DR: using Docker is an anti-pattern > Big images > Requiring rebuilds for every single change > Forcing things to run in containers > Using overly comple
by musicale 5y ago
TL;DR: using Docker is an anti-pattern
> Big images
> Requiring rebuilds for every single change
> Forcing things to run in containers
> Using overly complex tools
> Building with Dockerfiles
- justin_oaks 5y agoWhile I won't address each item in your list. I'll say that I love Dockerfiles. They make it clear what steps occurred to arrive at the resulting image. For any image that is built from an open-source repository, I can find the Dockerfile, look at it and say "Oh, that's how they did it!" In the article it says that Dockerfiles might not be the best way to build your image. I think some of that may have come from before the days of multi-stage builds. With multi-stage builds you can use a lot of tools (like the Go compiler) at build time without including those tools in your final build. Can we do better than Dockerfiles as they are today? I'm sure we can, but can I appreciate what I have while knowing it could be better.
- musicale 5y agoThe listed points (>) are quoted from the article.
- BossingAround 5y agoDocker containers are easy to build in a way that's pretty bad. I don't think that necessarily implicates Docker containers as a bad tech. In the same way, you can write an insert language here application that's horribly unmaintainable, and that tells you nothing of the language. I don't like Docker as a company, but I can't imagine living my tech life without containers + Kubernetes, and Dockerfiles are really easy to write and read.
- musicale 5y agoExactly - for most people, "using docker" is equivalent to invoking these anti-patterns, usually because it is the path of least resistance. Unfortunately avoiding the anti-patterns seems to be much harder than adopting them.