Basically Everyone Should Be Avoiding Docker

Post by [deleted] » Mon, Jul 07, 2025, 7:58 AM UTC

ndsipa_pomu wrote: post #90

rascul wrote: post #83

Earlier quoted context omitted.

By default there is no assurance that any external resource you use is going to be the same every time. Whether that's another image, a package you install, etc. This is something you have to ensure yourself if you want it to be actually reproducible. Specifying a specific version or hash of an external resource can help get you there.

Thanks - that makes sense now. I was thinking of "reproducible" as in it does the same thing each time, but as you say, that can lead to different outcomes - usually updated or patched versions of base images etc.

Post by hadlock » Mon, Jul 07, 2025, 6:25 PM UTC

dima55 wrote: post #39

kousthub wrote: post #33

Why would you edit or delete files inside a running container? It’s ephemeral and supposed to be used stateless. You can attach volumes from host system if you need persistence.

Because there are different use cases. About 100% of the people I talk to that use docker, are using it to make a separate set of dependencies available in a possibly-different distribution. For THOSE people, the ephemeral, stateless nature of docker is a huge detriment in usability, and a chroot would be far more appropriate. I see docker users waste countless hours working around its statelessness. All the time. YM…