A Decade of Docker Containers

Re:A Decade of Docker Containers by osigurdson on Saturday March 07, 2026 @02:40PM (#47290793)

In some situations, yes, others no. For instance if you want to control memory or cpu using a container makes sense (unless you want to use cgroups directly). Also if running Kubernetes a container is needed.

[ Parent | on HN ]

Re:A Decade of Docker Containers by matrss on Saturday March 07, 2026 @02:59PM (#47290958)

You have to differentiate container images, and "runtime" containers. You can have the former without the latter, and vice versa. They are entirely orthogonal things.

E.g. systemd exposes a lot of resource control as well as sandboxing options, to the point that I would argue that systemd services can be very similar to "traditional" runtime containers, without any image involved.

[ Parent | on HN ]

Re:A Decade of Docker Containers by osigurdson on Saturday March 07, 2026 @08:14PM (#47293301)

Well, I did mention "or use cgroups" above.

[ Parent | on HN ]

Re:A Decade of Docker Containers by matrss on Sunday March 08, 2026 @09:07AM (#47297012)

And what I've said is that there are more options. You don't have to use cgroups directly, there are other tools abstracting over them (e.g. systemd) that aren't also container runtimes.

[ Parent | on HN ]