Hacker News Reader

Comment by meddlepal | Hacker News Reader

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 a the front page of a website known for debating the content of said articles.

View on HN

You should read articles without assuming Hacker News is the intended audience. They usually aren't submitted by the author.

> I'm facepalming because he literally went through all the effort to replace Docker without fixing the underlying problem which is his script.

Well, he didn't say that the reoccurring problem came back, so maybe it was Docker after all?

Either way, I agree somewhat #facepalm

No, some container went rogue, and in the process dragged the Docker daemon which annoyed him PLUS he'd learnt that it was possible to run containers rootless and daemonless SO he changed his setup. Please RTFA.

Docker 19.03 has a rootless option

https://github.com/moby/moby/blob/master/docs/rootless.md

https://news.ycombinator.com/item?id=20542915

Last I checked it isn't out yet and Podman offers this already.

Not the default hence not well tested. AND you still have a Docker daemon running. Furthermore, last time I checked, Docker does not support user namespacing in a released version yet.

I maintain the "duh fix your script dummy" is not the right attitude. The author clearly states it's used for a build farm. That is bound to fail ...

I read "Docker daemon was using 100% CPU" to be the recurring incident; not a given script. And when that happens, it ends up cascading and stuff get OOM-killed before you know it.

You missed the point. RedHat has replaced the docker command with their own tool that does the same thing. He's just trying the new tools and it's poorly framed as a deliberate migration. It's not a migration and there is no effort involved. Docker is simply gone, the tools he mention are the new de facto standard and he will have to live with them anyway.

Reply on news.ycombinator.com