81–90 of 103 posts
Earlier quoted context omitted.
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
Great points in this thread, but I would say another advantage of Docker is that of documentation. The Dockerfile is a description of a reproducible build, and a docker-compose.yml file documents how running services interact, which ports are exposed, any volumes that are shared, etc. It’s all too easy for config knowledge to be siloed in people. I got the impression that the Author prefers tinkering with pet servers…
> The Dockerfile is a description of a reproducible build It's not inherently reproducible but it can potentially be made so.
Earlier quoted context omitted.
> The Dockerfile is a description of a reproducible build It's not inherently reproducible but it can potentially be made so.
How is it not reproducible?
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.
Docker is not about enterprise. It is about having a standard format for relaying configuration and install instructions to produce a reproducible dev or production environment on any hardware or OS.
If you don’t take the time to do that with your open source project… yeah I ain’t touching it with a 10ft pole.
> Well, if you’re expecting Docker to have a file-system easily accessible, you’re wrong—in fact, that’s “the point.” I can’t use typical commands like updatedb/locate/find to find what I need. I have to run a command with a massive prefix specific to that container. I don’t have tab completion when running Docker container commands, so when I inevitably mistype while searching for the file or attempting to delete it…
No you're not missing anything, aside from the small part of containers that are "FROM scratch" and don't have a shell binary, you can do the command you wrote. The author didn't seem to research how to use Docker before writing this.
"Ergo, I don’t use Docker and containerization, I’m annoyed by them and I don’t do tutorials on them. They are not for me or for people who want to do basic personal sysadmining. I think enterprise sysadmins would definitely do better doing more for their personal life outside of things like Docker, but again, there are reasons people use these things for many professional use-cases."
Earlier quoted context omitted.
How is it not reproducible?
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.