Document and test distro-specific unit differences (Arch, CentOS, Ubuntu, AlmaLinux) #3

Open
opened 2026-04-03 13:57:12 +00:00 by sgcommand · 0 comments
Member

Investigate and document any differences in generated unit files across major Linux distributions.

Known differences to check

  • Binary paths: /usr/bin/podman vs /usr/local/bin/podman on some distros
  • WantedBy target names
  • User unit lingering requirements (loginctl enable-linger) for rootless containers
  • SELinux considerations on CentOS/AlmaLinux
  • docker.service vs podman.socket as dependency depending on distro defaults

Deliverables

  • docs/distros.md with per-distro notes
  • Consider a --runtime-path config option or auto-detection via which
  • Test matrix in CI if possible
Investigate and document any differences in generated unit files across major Linux distributions. ## Known differences to check - Binary paths: `/usr/bin/podman` vs `/usr/local/bin/podman` on some distros - `WantedBy` target names - User unit lingering requirements (`loginctl enable-linger`) for rootless containers - SELinux considerations on CentOS/AlmaLinux - `docker.service` vs `podman.socket` as dependency depending on distro defaults ## Deliverables - `docs/distros.md` with per-distro notes - Consider a `--runtime-path` config option or auto-detection via `which` - Test matrix in CI if possible
Sign in to join this conversation.