History

Valentin Rothberg 38bb6756b8 podman.service: set type to simple Set the type of the podman.service to simple. This will correctly report the status of the service once it has started. As a oneshot service, it does not transition from the startup state to running. Signed-off-by: Valentin Rothberg <rothberg@redhat.com>		2020-07-20 11:42:49 +02:00
..
auto-update	auto updates	2020-03-17 17:18:56 +01:00
system	podman.service: set type to simple	2020-07-20 11:42:49 +02:00
README.md	[CI:DOCS]fix systemd files for apiv2	2020-02-06 15:34:09 -06:00
user	systemd: symlink user->system	2020-07-20 11:12:41 +02:00

README.md

Setting up Podman service for systemd socket activation

system-wide (podman service run as root)

copy the podman.service and podman.socket files into /etc/systemd/system
systemctl daemon-reload
systemctl enable podman.socket
systemctl start podman.socket
systemctl 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.service and podman.socket files into ~/.config/systemd/user
systemctl --user enable podman.socket
systemctl --user start podman.socket
systemctl --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.