mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-28 03:07:56 +00:00
Replace multi-user.target with default.target across the code base.
It seems like the multi-user one is not available for (rootless) users
on F35 anymore is causing issues in all kinds of ways, for instance,
enabling the podman.service or generated systemd units.
Backport of commit
|
||
|---|---|---|
| .. | ||
| auto-update | ||
| system | ||
| README.md | ||
| user | ||
Setting up Podman service for systemd socket activation
system-wide (podman service run as root)
- copy the
podman.serviceandpodman.socketfiles into/etc/systemd/system systemctl daemon-reloadsystemctl enable podman.socketsystemctl start podman.socketsystemctl status podman.socket podman.service
Assuming the status messages show no errors, the libpod service is ready to respond to the APIv2 on the unix domain socket /run/podman/podman.sock
podman.service
You can refer to this example for a sample podman.service file.
podman.socket
You can refer to this example for a sample podman.socket file.
user (podman service run as given user aka "rootless")
mkdir -p ~/.config/systemd/user- copy the
podman.serviceandpodman.socketfiles into~/.config/systemd/user systemctl --user enable podman.socketsystemctl --user start podman.socketsystemctl --user status podman.socket podman.service
Assuming the status messages show no errors, the libpod service is ready to respond to the APIv2 on the unix domain socket /run/user/$(id -u)/podman/podman.sock
podman.service
You can refer to this example for a rootless podman.service file.
podman.socket
You can refer to this example for a rootless podman.socket file.