mirror of
				https://github.com/containers/podman.git
				synced 2025-11-01 02:42:11 +08:00 
			
		
		
		
	 6f1c7a0b6b
			
		
	
	6f1c7a0b6b
	
	
	
		
			
			Require the network to be online in all (generated) systemd units to make sure that containers and Podman run only after the network has been fully configured. Fixes: #10655 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
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.