This may be familiarity bias, but I often find `kubectl` and related tools like `k9s` more ergonomic than `systemctl`/`journalctl`, even for managing simple single-replica processes that are bound to the host network.
Systemd seems to be moving in that direction, the features are coming together to actually enable this.
Though imagining the unholy existence of an init system who's only job is to spin up containers, that can contain other inits, OS images, or whatever ..... turtles all the way down.
This may be familiarity bias, but I often find `kubectl` and related tools like `k9s` more ergonomic than `systemctl`/`journalctl`, even for managing simple single-replica processes that are bound to the host network.
See Podman quadlets.
Remember fleet?
Systemd is on the wrong layer here. You need something that can set your machine up, like docker.
Systemd seems to be moving in that direction, the features are coming together to actually enable this.
Though imagining the unholy existence of an init system who's only job is to spin up containers, that can contain other inits, OS images, or whatever ..... turtles all the way down.
I don't see why not. Maybe it should be on the same layer going forward - for true cloud compute (including on-premise cloud)
Docker does not set your machine up: it sets your process up.
Tech like Flatpak or Snap is closer to Docker than "machines" are — except that Docker has local, virtualized networking built-in as the IPC layer.
Okay it sets the machine up, but not the underlying host machine though.