Live data from Hacker News

Basically Everyone Should Be Avoiding Docker

lukesmith.xyz

31–40 of 103 posts

Re: Basically Everyone Should Be Avoiding Docker

#32

I like docker because it makes it super easy to try out apps that I don’t necessarily know that I want and I can just delete it. I’m also confused about the claim that there is no config file… everyone I know uses docker compose, that’s really the only right way to use docker, using a single docker command is for testing or something, if you’re actually using the app long term, use docker compose. Also most apps I us…

The title should be the opposite imo. Why everyone should use docker

Re: Basically Everyone Should Be Avoiding Docker

#34

Earlier quoted context omitted.

When I encounter a README/INSTALL that advises Docker, I start to suspect that the package is a mess. I'm sure there are legitimate usages within enterprise-y scenarios, but it has commonly become a way to paper over other issues.

This is definitely true. You see it constantly in deep learning applications, where eg NVIDIA’s fancy fp8 stuff needs C++11 ABI, so they need to compile torch from source, which means everything with C++ dependencies on torch needs to be recompiled, and eventually it’s much easier to ship a container image. It can be done with an Ansible playbook, sure, if you don’t have to ever do anything else with your machine.

One of the best things about docker that is not mentioned often enough is how it keeps your host machine clean.

Re: Basically Everyone Should Be Avoiding Docker

#35

Should this be titled "Basically everyone who doesn't know how to use Docker should be avoiding Docker"?

Agreed. I really tire of flat, authoritative statements with no room for context or clarification. Perhaps that's what's needed to succeed in a VC world, but it's the easiest way to get me to dismiss the author's opinion because they leave no room for discussion.

Re: Basically Everyone Should Be Avoiding Docker

#36

Earlier quoted context omitted.

it really does allow easy setup with compose, multiple containers, different versions, etc. I have been setting up linux servers and desktops for decades but docker made it way easier for a lot of things I still have email server setups I would never dare try to touch with docker, but I know it is possible like a lot of things it has its uses and it's really good at what it does

i love the convenience and ease-of-use but worry about the security compared to full-blown vm

Kata containers is a nice compromise. Each container is run as a microvm

Re: Basically Everyone Should Be Avoiding Docker

#37
This reads less like an article about the downsides of Docker and more like an article about how someone doesn’t fully understand Docker.

Not that I think Docker should always be used. It’s a simple piece tech on the surface but explodes in complexity the more complicated you try to get.

All that said, this article feels detached from reality.

Re: Basically Everyone Should Be Avoiding Docker

#39

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. YMMV

Re: Basically Everyone Should Be Avoiding Docker

#40

This has rather strong “old man yelling at clouds” vibes. OP: Learn docker and it stops being an “impenetrable wall.” Face it, you don’t want to use docker (or podman) because you are set in your ways. That’s fine, but it is not an argument for anyone else.

When I encounter a README/INSTALL that advises Docker, I start to suspect that the package is a mess. I'm sure there are legitimate usages within enterprise-y scenarios, but it has commonly become a way to paper over other issues.

"We paid zero attention to the absolute hell of dependencies we were creating for ourselves, and eventually decided to just ship a docker image of the smart intern's laptop "
Post reply on HN