Re:Replacing Kubernetes with systemd (2024)
by mattbillenstein on Monday May 05, 2025 @07:46PM
(#43900516)
I never moved to containers and seeing the churn the community has went through with all of this complicated container tooling, I'm happy orchestrating small-scale systems with supervisord and saltstack-like chatops deployments - it's just stupid simple by comparison and provides parity between dev and prod environments that's nice.
[ Parent
| on HN ]
Re:Replacing Kubernetes with systemd (2024)
by baggy_trough on Monday May 05, 2025 @07:55PM
(#43900584)
try the built-in systemd containers - via nspawn. Underrated tool!
Re:Replacing Kubernetes with systemd (2024)
by candiddevmike on Monday May 05, 2025 @08:08PM
(#43900654)
Too many gaps around image management. It seems like an unfinished feature that wasn't completely thought out IMO. Podman is what systemd-nspawns OCI interface should've become.
Re:Replacing Kubernetes with systemd (2024)
by MrDrMcCoy on Tuesday May 06, 2025 @01:36AM
(#43902095)
The incomplete resource controls compared with other units is also annoying. Probably the biggest reason for me that I haven't used nspawn much.
Re:Replacing Kubernetes with systemd (2024)
by baggy_trough on Tuesday May 06, 2025 @02:42PM
(#43908319)
What's an example of that?
It looks like supervisord had it last release in December 2022. GitHub issue for a new release are not answered: https://github.com/Supervisor/supervisor/issues/1635#issue-2...
The original author seems to have moved on to NixOS.
Re:Replacing Kubernetes with systemd (2024)
by mardifoufs on Monday May 05, 2025 @11:01PM
(#43901427)
What churn? For 95% of users, the way to use containers hasn't changed in the past decade. It's just a combination of docker CLI, maybe some docker compose for local testing and then pushing that image somewhere.
Re:Replacing Kubernetes with systemd (2024)
by mattbillenstein on Tuesday May 06, 2025 @01:41PM
(#43907714)
True perhaps from a certain perspective, but k8s and the other orchestration technologies, etc. Also dev workflows in containers seem broken and hard - I think it offers a poor experience generally.