51–60 of 95 posts
> podman pull downloads get all layers in parallel, in contrast to Docker’s. Hmm? I could have sworn docker pulled multiple layers at once the last time I used it.
Docker pulls three layers at a time, not all of them.
> was likely due to a script that had got out of hand starting up too many containers. So there wasn't any actual problem with Docker, it was the OP's own problem that they "solved" by switching container platforms instead of just fixing their own buggy script?
Earlier quoted context omitted.
> you could argue systemd shouldn’t be a daemon too and sysv init scripts are better too. You certainly could.
And you'd be wrong... The init system will always be a daemon, for obvious reasons ;-)
I personally like keeping my root partition to a minimal and ever since docker came into the picture I keep running into spacing issues. So the allure for me to switch isn't technical but for peace of mind storing images in userspace
https://docs.docker.com/engine/reference/commandline/dockerd...
I’ve managed to resist the hype and still not ever used docker for anything ... I still really struggle to understand what the practical benefits to this kind of containerization actually are ... It seems like people reach for it because they want to have some kind of “compile target” into which they can stick “all the things” their application needs to run — which is supposed to then help them “deploy” into their de…
The biggest benefit for edX, which is where I started using Docker and gained the most experience, was being able to get developers up and running with our key services in a couple hours as opposed to days. Everything is scripted, and ephemeral. Broke something? Refresh the environment. Want to try a new configuration? Build a new image. This was not as easy in our previous Vagrant devstack. > Don’t you still inevita…
I’ve managed to resist the hype and still not ever used docker for anything ... I still really struggle to understand what the practical benefits to this kind of containerization actually are ... It seems like people reach for it because they want to have some kind of “compile target” into which they can stick “all the things” their application needs to run — which is supposed to then help them “deploy” into their de…
I’ve managed to resist the hype and still not ever used docker for anything ... I still really struggle to understand what the practical benefits to this kind of containerization actually are ... It seems like people reach for it because they want to have some kind of “compile target” into which they can stick “all the things” their application needs to run — which is supposed to then help them “deploy” into their de…
Earlier quoted context omitted.
I facepalmed when I read that... This is an all too common problem in development and it's made me very skeptical of coworkers at times who use it "X technology doesn't work or X is garbage" as a justification to switch technologies or spend time prototyping several alternatives. I'm not gonna say Docker is a perfect tool by any stretch either.
Very true. I know a lot of people in school who have to use a generally well regarded technology, but hate it because they had to use it in a class. For example, they might see someone on github and go “oh is that github? I hate using git” when in reality they had to use it in a group project with 4 other people who have never used it, and had no understanding of branches, merging, etc. I have seen the same thing wit…
(ProTip: Maybe you hated it from school because it was used as a tool for teaching theory and beginner stuff, and you were given difficult homework assignments. Maybe you'd like it more if you learned how to use it practically, while you were working on things you actually wanted to do.)