| podman.service is socket activated through podman.socket. It should not have its own [Install] section, it does not make sense to systemctl enable podman.service. This leads to podman.service always running on a Debian system, as Debian's policy is to enable/start running services by default. We don't want a daemon :^) Fixes: #7190 Reported-by: @martinpitt Signed-off-by: Valentin Rothberg <rothberg@redhat.com> | ||
|---|---|---|
| .. | ||
| auto-update | ||
| system | ||
| README.md | ||
| user | ||
		
			
				
				README.md
			
		
		
			
			
		
	
	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-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.serviceandpodman.socketfiles 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.