Re:Docker, Django, Traefik, and IntercoolerJS: My go-to stac...
by mherrmann on Sunday January 31, 2021 @03:14AM
(#25977078)
I've never encountered this "dangling libraries" problem you describe in the past 7 years of developing web apps. I suspect you are working in different, maybe more specialised, environments than me. For me, it usually is really just pretty standard libraries and dependencies.
Re:Docker, Django, Traefik, and IntercoolerJS: My go-to stac...
by antidocker on Sunday January 31, 2021 @05:56AM
(#25977849)
This is wrong. Docker is a VM on Windows at least.
Re:Docker, Django, Traefik, and IntercoolerJS: My go-to stac...
by sofixa on Sunday January 31, 2021 @12:51PM
(#25980788)
Nobody is talking about Docker on Windows or Mac for production use.
Re:Docker, Django, Traefik, and IntercoolerJS: My go-to stac...
by antidocker on Sunday January 31, 2021 @11:46PM
(#25985641)
Don't you think Mac are not used in Prod?
On the contrary, it's easier to debug with Docker - it eliminates dangling system level libraries / old dependencies / cache, and everything is self-contained. If you have the problem in dev, you'll have it in prod as well.
Docker is not a VM, it's basically a big wrapper around chroot and cgroups, the performance hit is minimal. The advantage is that, again, it's self-contained, so there's little risk some OS / dangling library muddies the waters ( especially in Python that's a great risk -OS level python library installations are a thing, and many a Python library depend on C libraries on the system level, which you can't manage through Python tooling). It's also idempotent ( thus making rollbacks easier) and declarative.