Everybody should use Podman instead :P
Basically Everyone Should Be Avoiding Docker
61–70 of 103 posts
Re: Basically Everyone Should Be Avoiding Docker
#62> 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.
Re: Basically Everyone Should Be Avoiding Docker
#63Containerization is amazingly great for scientific computing. I don’t ever want to go back to doing the make && make install dance and praying I’ve got my dependency ducks in a row.
Containerization is great. Docker != containerization. Most people don't even know it runs qemu under the hood.
Do you have info on this ?
I only found that it can use qemu to build or run images for a different cpu architecture that your computer.
Why would it use qemu ? Docker is not doing virtualization but containerization
Re: Basically Everyone Should Be Avoiding Docker
#64Why all of the lukesmith posts get flagged even the landchad website thar was just tutorials?
Re: Basically Everyone Should Be Avoiding Docker
#65Docker has so much overhead (complexity and technical) - I hear people recommend it for simplicity all the time and assume they have out-of-date, insecure setups ... Docker containers require more setup to secure and backup in my experience.
> require more setup to secure
docker is not secure. It has no "real" security boundry, and any malicious actor could have you run a docker image that is just as malware as an executable. Like locks on doors, it just keeps out the honest people. So i say effort spent trying to secure it is wasted.
> backup
if you have data in the docker instance, you have to use volume mounts, and then backup that volume mount. I say it's easier to backup than an installed app, as you cannot be sure that it didnt write somewhere else their data!
Re: Basically Everyone Should Be Avoiding Docker
#66Luke, if you want to interactively run commands like “find” like you are used to, you can run:
“docker exec -it my_container bash”
Though there are many reasons why you wouldn’t want to go in and delete a file since that won’t persist or be reproducible.
Re: Basically Everyone Should Be Avoiding Docker
#67"Everyone else needs to learn and use Linux so I don't have to learn Docker"
Yeah, what I don't understand is that he seems to completely ignore the fact that a docker containers is still running linux, just isolated in a new filesystem (and more technologies I don't know a lot about like namespaces and stuff)
So the author thinks it's better for users to do (sometimes tedious) steps to get an application or a set of applications running, just for them to "know how to use linux", while ignoring the fact that Docker/containerization's primarily use case is for the developer side, and the developer needs to know linux to write a working Dockerfile.
Re: Basically Everyone Should Be Avoiding Docker
#68> 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…
Yes if they want to edit the running container config, that is exactly what to do. Also, if you are just running a mounted volume for the configs, you don't even have to go that far. You can just edit the mounted volume on the host machine and it will show up immediately in the container.
However, I would think you would want to edit the Dockerfile instead so that you fix it every time you restart the container.
But I think the whole point of this post is that the author has no idea how docker works and is mad about having to learn docker things, so nobody should use them. Never mind the entirety of cloud infrastructure running in containers and doing amazing things. Never mind being able to duplicate state across tons of different servers at the same time. It shows that the author isn't into making infrastructure at scale, and has no idea how incredible docker has been to software development, CI/CD pipelines, and deployment / release infrastructure as a whole.
Re: Basically Everyone Should Be Avoiding Docker
#69I get the impression that the person who wrote this article doesn't know much about docker. Running 2 apps and a certbot can be done without containers easily. Try running 20 apps, some of which depend on having the same dependency but on a different version.
Regarding security, it depends on how you set up your containers. If you just run them all with default settings - the root user; and give them all the permissions, then yeah, quite insecure. But if you spend an extra minute and create a new non-root user for each container and restrict the permissions then it's quite secure. There are plenty of docker hardening tutorials.
Regarding ease of setup, it took me a while to learn docker. Setting up first containers took very long time. But now, it's quick and easy. I have templates for the docker compose file and I know how to solve all the common issues.
Regarding ease of management, it's very easy. Most of my containers is setup once and forget. Upgrading an app just requires changing the version in the docker-compose file.
Re: Basically Everyone Should Be Avoiding Docker
#70Hmmm this reads like the author neither understands Docker or Linux, many of the issues they seem to have is just stuff they don't know the right approach to tackling.
Imagine pairing with a mid/Sr and watching them scroll up 40 commands in the terminal and they are complaining that bash won't let them up-arrow 10 lines at a time. In this case, someone writes 5000 words about how they can't get certbot working with their docker setup. They would benefit a lot from working with someone who knows what they are doing.