81–90 of 95 posts
> I’d never really got to the bottom of it Perhaps it might have been worth the extra time to get to the bottom of it instead of switching and, in the end, not noticing any big differences? Also, I noticed there was an ad at the end of the post for the book Docker in Practice . Ironic placement.
Wait, isn't the author of the blog post the author of the book?
Earlier quoted context omitted.
Well for one, it can restart the container when it fails or on boot up. I don’t see how having no process minder improves anything, you could argue systemd shouldn’t be a daemon too and sysv init scripts are better too.
Systemd not being a daemon doesn't make any sense; both it and SysV are init systems which are by necessity daemonized processes.
https://docs.docker.com/config/containers/resource_constrain...
Docker can really grind if it starts hitting swap. I have not added resource constraints but I've been planning on doing it.
Earlier quoted context omitted.
> I still really struggle to understand what the practical benefits to this kind of containerization actually are ... Here's why I started using it years ago. I had a CentOS 6 machine that I wanted to run Plex, Subsonic and Transmission on, but I couldn't, because they had different (EDIT: and conflicting) requirements for various packages. I might have been able to hack it, but it was looking really tricky. Enter Do…
If you didn't have that requirement of conflicting packages, would you still have used docker? Isn't once a year update a large security risk?
Earlier quoted context omitted.
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…
>git...LaTeX, Python, and Vim To be fair, LaTeX, git, and Vim, beyond shallow use, have fairly steep learning curves and can initially seem like a huge inconvenient mess before one learns, through trial and error, enough of the basics to really unlock enough utility to justify their use. In a perfect world we'd all first sit down with manuals/tutorials, absorb everything from the getgo, and hack away with bliss; but…
Vi predates keyboards with arrow keys and numpad. You can do most of what vim can do in any editor if you can use your keyboard effectively. Then there is the question of VI vs VIM. Some schools force students to use VI, which is really a different and antiquated beast.
LaTeX lost a lot of relevance since Office 2010, that added a great equations editor and better handling of sections/subsections.
Earlier quoted context omitted.
Systemd not being a daemon doesn't make any sense; both it and SysV are init systems which are by necessity daemonized processes.
That’s the point. The same principle applies to Docker. Although conceivably the daemon could be just about process/container management instead of image management as well.
Earlier quoted context omitted.
It was on his home servers and he got a valid point regarding redundant daemon in docker. So I don't understand why you facepalm because its not your business what he runs at home or how he rocks his boat.
I'm facepalming because he literally went through all the effort to replace Docker without fixing the underlying problem which is his script. At a minimum it means he doesn't understand how his own code works which is going to be problematic if your career involves coding. The "it's none of your business" argument falls flat the moment you decide to broadcast to the entire world what you're doing and then get it onto…
Earlier quoted context omitted.
Because they have to use a hypervisor to get the benefits of the Linux kernel. If you want to speed things up and get native benefits then try switching to Linux or convince Apple to add native containers.
Is Docker faster on Windows/WSL than Macs?
Earlier quoted context omitted.
And you'd be wrong... The init system will always be a daemon, for obvious reasons ;-)
You're begging the question that systemd should be the init system
> systemd shouldn’t be a daemon too
A. False.
> and sysv init scripts are better too
B. Debatable, but the start is a false premise, SysV init was a daemon plus the scripts.