Podman - Revision history

Ingrate one at 14:32, 5 May 2026

2026-05-05T14:32:54Z

← Older revision		Revision as of 14:32, 5 May 2026
Line 83:		Line 83:

	This problem may be solved by replacing [[runc\|runc]] by [[runc#Crun\|Crun]] and recreating your container. Keep in mind that {{Pkg\|crun}} replaces {{Pkg\|runc}}, which will render containers made with the latter unusable until recreated.		This problem may be solved by replacing [[runc\|runc]] by [[runc#Crun\|Crun]] and recreating your container. Keep in mind that {{Pkg\|crun}} replaces {{Pkg\|runc}}, which will render containers made with the latter unusable until recreated.

			=== Error: netavark: iptables: No such file or directory (os error 2) ===

			Podman depends on {{Pkg\|iptables}} package:
			{{cmd\|# apk add iptables}}

	== See also ==		== See also ==

Prabuanand: slight rephrasing, added wikilink and external reference

2025-09-24T03:23:08Z

slight rephrasing, added wikilink and external reference

← Older revision		Revision as of 03:23, 24 September 2025
Line 1:		Line 1:
	[https://podman.io/ Podman] is a utility provided as part of the libpod library. It can be used to create and maintain containers. Podman (Pod Manager) is a fully featured container engine that is a simple daemonless tool.		[https://podman.io/ Podman] is a utility provided as part of the libpod library. It can be used to create and maintain containers. Podman (Pod Manager) is a fully featured container engine that is a simple daemonless tool. In Alpine linux, [[Distrobox]] automatically installs and uses Podman.

	== Installation ==		== Installation ==
Line 10:		Line 10:
	# rc-service cgroups start</nowiki>}}		# rc-service cgroups start</nowiki>}}

	~~If you are running on top of [[Btrfs]], consider setting~~ storage driver ~~to <code>btrfs</code>:~~ {{~~Cmd~~\|~~$ cat~~ /etc/containers/storage.conf \| ~~grep 'driver ='~~}}		The default storage driver setting in {{Path\|/etc/containers/storage.conf}} is {{ic\|overlay}}. If you're running podman inside a container or using [[Btrfs]] filesystem, change the storage driver to {{ic\|vfs}} or {{ic\|btrfs}} respectively.
	~~driver = "btrfs"~~
	If you're running podman inside a container, change the storage driver to ~~<code>~~vfs~~</code>~~

	You might need to restart your machine at this stage for the above changes to work properly.		You might need to restart your machine at this stage for the above changes to work properly.
Line 85:		Line 83:

	This problem may be solved by replacing [[runc\|runc]] by [[runc#Crun\|Crun]] and recreating your container. Keep in mind that {{Pkg\|crun}} replaces {{Pkg\|runc}}, which will render containers made with the latter unusable until recreated.		This problem may be solved by replacing [[runc\|runc]] by [[runc#Crun\|Crun]] and recreating your container. Keep in mind that {{Pkg\|crun}} replaces {{Pkg\|runc}}, which will render containers made with the latter unusable until recreated.

			== See also ==

			* [https://docs.podman.io/en/latest/ Official Podman Documentation]

	[[Category:Virtualization]]		[[Category:Virtualization]]

Prabuanand: rephrased sentence

2025-09-23T04:55:17Z

rephrased sentence

← Older revision		Revision as of 04:55, 23 September 2025
Line 7:		Line 7:
	== Configuration ==		== Configuration ==

	To run podman you'll need to enable the ~~<code>~~cgroups~~</code>~~ service. {{Cmd\|<nowiki># rc-update add cgroups		To run podman with full functionality you'll need to enable the [[OpenRC#cgroups\|cgroups]] service in v2 or '''unified''' mode, which is the current default. {{Cmd\|<nowiki># rc-update add cgroups
	# rc-service cgroups start</nowiki>}}		# rc-service cgroups start</nowiki>}}

	~~In the past cgroups v2 needs to be enabled in OpenRC. Currently this is the default setting in [[OpenRC#cgroups v2\|cgroups v2]].~~

	If you are running on top of [[Btrfs]], consider setting storage driver to <code>btrfs</code>: {{Cmd\|$ cat /etc/containers/storage.conf \| grep 'driver ='}}		If you are running on top of [[Btrfs]], consider setting storage driver to <code>btrfs</code>: {{Cmd\|$ cat /etc/containers/storage.conf \| grep 'driver ='}}

Prabuanand: moved troubleshooting section from Distrobox page created by user Lilith

2025-09-23T03:47:02Z

moved troubleshooting section from Distrobox page created by user Lilith

← Older revision		Revision as of 03:47, 23 September 2025
Line 23:		Line 23:

	=== Running in rootless mode ===		=== Running in rootless mode ===

			To avoid [[#Permission problems with rootless podman\|permission problems]] with rootless podman, consider using [[runc#Crun\|Crun]].

	To run podman in rootless mode, run the following commands. Replace <USER> with your username in the following commands: {{Cmd\|<nowiki># modprobe tun		To run podman in rootless mode, run the following commands. Replace <USER> with your username in the following commands: {{Cmd\|<nowiki># modprobe tun
Line 77:		Line 79:
	You might want to fix this temporarily, for currently running system by issuing the command:{{ic\|# mount --make-rshared /}}		You might want to fix this temporarily, for currently running system by issuing the command:{{ic\|# mount --make-rshared /}}
	Alternately, refer to [[#Shared mount\|Shared mount]] section for permanent solution(s).		Alternately, refer to [[#Shared mount\|Shared mount]] section for permanent solution(s).

			=== Permission problems with rootless podman ===

			You may encounter an error when entering your rootless container:

			<code>Error: unable to start container "XYZ": runc: runc create failed: unable to start container process: unable to apply cgroup configuration: rootless needs no limits + no cgrouppath when no permission is granted for cgroups: mkdir /sys/fs/cgroup/XYZ: permission denied: OCI permission denied</code>

			This problem may be solved by replacing [[runc\|runc]] by [[runc#Crun\|Crun]] and recreating your container. Keep in mind that {{Pkg\|crun}} replaces {{Pkg\|runc}}, which will render containers made with the latter unusable until recreated.

	[[Category:Virtualization]]		[[Category:Virtualization]]

Prabuanand: added minor rewording

2025-07-20T03:33:32Z

added minor rewording

← Older revision		Revision as of 03:33, 20 July 2025
Line 32:		Line 32:

	=== Getting socket ===		=== Getting socket ===
	~~You do not need the socket if you are only using the podman CLI locally.~~
	~~If you want to~~ use the podman API or use podman remotely, you need ~~the~~ podman socket.		To use the podman API or use podman remotely, you need podman socket. Socket is not needed, if podman CLI is used locally.
	~~You can~~ get ~~it by starting~~ the podman service: {{Cmd\|rc-service podman start}}		To get socket, start the podman service: {{Cmd\|# rc-service podman start}}
	The default location of the socket is {{Path\|/run/podman/podman.sock}}.		The default location of the socket is {{Path\|/run/podman/podman.sock}}

	=== Shared mount ===		=== Shared mount ===

Liliace: Add how to get podman socket

2025-07-20T01:44:13Z

Add how to get podman socket

← Older revision		Revision as of 01:44, 20 July 2025
Line 30:		Line 30:

	Run an example container to verify everything works: {{Cmd\|$ podman run --rm hello-world}}		Run an example container to verify everything works: {{Cmd\|$ podman run --rm hello-world}}

			=== Getting socket ===
			You do not need the socket if you are only using the podman CLI locally.
			If you want to use the podman API or use podman remotely, you need the podman socket.
			You can get it by starting the podman service: {{Cmd\|rc-service podman start}}
			The default location of the socket is {{Path\|/run/podman/podman.sock}}.

	=== Shared mount ===		=== Shared mount ===

Prabuanand: fixed wikitag

2025-06-02T10:48:38Z

fixed wikitag

← Older revision		Revision as of 10:48, 2 June 2025
Line 34:		Line 34:

	Containers on linux might require filesystems to be mounted with different propagation than the kernel default of 'private'.		Containers on linux might require filesystems to be mounted with different propagation than the kernel default of 'private'.
	{{Cmd\|$ findmnt -o PROPAGATION /		{{Cmd\|$ findmnt -o PROPAGATION /}} will produce the following output:
	PROPAGATION		PROPAGATION
	private}}		private

	This section explains few ways to mount your root('''/''') as shared for Distrobox to function. This is not needed when running in rootless mode.		This section explains few ways to mount your root('''/''') as shared for Distrobox to function. This is not needed when running in rootless mode.
Line 54:		Line 54:
	...}}		...}}

	For both the above cases, after a reboot test the working of shared '''/''' mount using the command: {{Cmd\|# findmnt -o PROPAGATION /		For both the above cases, after a reboot test the working of shared '''/''' mount using the command: {{Cmd\|# findmnt -o PROPAGATION /}} which will produce the following output:
	PROPAGATION		PROPAGATION
	shared}}		shared

	=== Docker compose ===		=== Docker compose ===

Prabuanand: moved additional solution for shared mount from Software management page

2025-06-02T10:43:41Z

moved additional solution for shared mount from Software management page

← Older revision		Revision as of 10:43, 2 June 2025
Line 31:		Line 31:
	Run an example container to verify everything works: {{Cmd\|$ podman run --rm hello-world}}		Run an example container to verify everything works: {{Cmd\|$ podman run --rm hello-world}}

	== ~~Troubleshooting~~ ==		=== Shared mount ===

	~~=== Shared mount ===~~		Containers on linux might require filesystems to be mounted with different propagation than the kernel default of 'private'.
			{{Cmd\|$ findmnt -o PROPAGATION /
			PROPAGATION
			private}}

	~~Containers on linux might require filesystems~~ to ~~be mounted with different propagation than the kernel default of~~ '~~private~~'. ~~If you see a warning:~~		This section explains few ways to mount your root('''/''') as shared for Distrobox to function. This is not needed when running in rootless mode.

	: ~~WARN[0000] "~~/~~" is not a shared~~ mount~~, this could cause issues or missing mounts with rootless containers~~		Method1:
			Fill in the file {{path\|/etc/local.d/mount-rshared.start}} as follows:{{Cat\|/etc/local.d/mount-rshared.start\|<nowiki>#!/bin/sh
			mount --make-rshared /</nowiki>}}

	~~you might want to fix this temporarily, for currently running system~~: {{~~Cmd~~\|# mount ~~--make~~-rshared /}}		Mark it as executable: {{cmd\|# chmod +x /etc/local.d/mount-rshared.start}}

	~~Try~~ the ~~command that caused the warning again~~.		Then enable the service to autostart through [[OpenRC]]. {{cmd\|<nowiki># rc-update add local default
			# rc-service local start </nowiki>}}

	~~Alternatively~~, ~~you could use following command:~~ {{~~Cmd~~\|~~# findmnt -o PROPAGATION~~ /}}		Method2:
	~~which should print~~:		An alternate solution with OpenRC v0.54.2-r1 onwards, edit the file {{path\|/etc/fstab}} and add {{ic\|shared}} option to the root partition such that:{{Cat\|/etc/fstab\|...
	~~PROPAGATION~~		/dev/sda2 / ext4 rw,relatime,shared 0 1
	~~shared~~		...}}

	For ~~a permanent fix (~~after a ~~[https:~~/~~/github.com/OpenRC/openrc/pull/526 OpenRC PR#526] is released - in newer version than 0.54.2-r1), edit {{path\|/etc/fstab}}~~:{{~~cmd~~\|# ~~$EDITOR /etc~~/~~fstab}}~~		For both the above cases, after a reboot test the working of shared '''/''' mount using the command: {{Cmd\|# findmnt -o PROPAGATION /
	~~Add <code>shared</code> option to the root partition:~~		PROPAGATION
	~~/dev/sda2 / ext4 rw,relatime,~~shared ~~0 1~~		shared}}
	~~and after a reboot test it out similarly as above.~~

	=== Docker compose ===		=== Docker compose ===

	The {{Pkg\|podman-compose}} package from provides a drop-in replacement for docker compose. Each time a docker compose is used, a warning will remind that this is using podman under the hood. This warning can be squelched permanently by running: {{cmd\|# touch /etc/containers/nodocker}}		The {{Pkg\|podman-compose}} package from provides a drop-in replacement for docker compose. Each time a docker compose is used, a warning will remind that this is using podman under the hood. This warning can be squelched permanently by running: {{cmd\|# touch /etc/containers/nodocker}}

			== Troubleshooting ==

			=== "/" is not a shared mount ===

			If you see a warning:
			: WARN[0000] "/" is not a shared mount, this could cause issues or missing mounts with rootless containers

			You might want to fix this temporarily, for currently running system by issuing the command:{{ic\|# mount --make-rshared /}}
			Alternately, refer to [[#Shared mount\|Shared mount]] section for permanent solution(s).

	[[Category:Virtualization]]		[[Category:Virtualization]]

Prabuanand: fixed wikitags, added headings, moved content

2025-06-02T10:02:39Z

fixed wikitags, added headings, moved content

← Older revision		Revision as of 10:02, 2 June 2025
Line 1:		Line 1:
			[https://podman.io/ Podman] is a utility provided as part of the libpod library. It can be used to create and maintain containers. Podman (Pod Manager) is a fully featured container engine that is a simple daemonless tool.

	== Installation ==		== Installation ==

	Podman can be installed via {{Pkg\|podman}} package in the community repository.		Podman can be installed via {{Pkg\|podman}} package in the community repository: {{Cmd\|# apk add podman}}

	~~{{Cmd\|# apk add podman}}~~		== Configuration ==

	~~=== Running as root ===~~		To run podman you'll need to enable the <code>cgroups</code> service. {{Cmd\|<nowiki># rc-update add cgroups
			# rc-service cgroups start</nowiki>}}

	~~To run podman you'll need~~ to ~~enable~~ the ~~<code>cgroups</code> service, consider enabling~~ [[OpenRC#cgroups v2\|cgroups v2]].		In the past cgroups v2 needs to be enabled in OpenRC. Currently this is the default setting in [[OpenRC#cgroups v2\|cgroups v2]].

	{{Cmd\|~~# rc-update add cgroups~~}}		If you are running on top of [[Btrfs]], consider setting storage driver to <code>btrfs</code>: {{Cmd\|$ cat /etc/containers/storage.conf \| grep 'driver ='}}
	~~{{Cmd\|# rc-service cgroups start}}~~		driver = "btrfs"
			If you're running podman inside a container, change the storage driver to <code>vfs</code>

	You might need to restart your machine for ~~this~~ to work properly.		You might need to restart your machine at this stage for the above changes to work properly.

	~~If you are running on top of [[Btrfs]], consider setting storage driver to <code>btrfs</code>:~~		=== Running as root ===

	{{Cmd\|~~$ cat /etc/containers/storage.conf \| grep 'driver ='~~}}		No further steps are required to run as root. Run an example container to verify everything works: {{Cmd\|# podman run --rm hello-world}}

	~~driver = "btrfs"~~

	~~If you're running inside a container, change the storage driver to <code>vfs</code>~~

	=== Running in rootless mode ===		=== Running in rootless mode ===

	~~For~~ rootless ~~support (replace~~ <USER> with your username):		To run podman in rootless mode, run the following commands. Replace <USER> with your username in the following commands: {{Cmd\|<nowiki># modprobe tun
			# echo tun >>/etc/modules
	{{Cmd\|# modprobe tun		# echo <USER>:100000:65536 >/etc/subuid
	&#~~35;~~ echo tun >>/etc/modules		# echo <USER>:100000:65536 >/etc/subgid </nowiki>}}
	&#~~35;~~ echo <USER>:100000:65536 >/etc/subuid
	&#~~35;~~ echo <USER>:100000:65536 >/etc/subgid}}

	Run an example container to verify everything works:		Run an example container to verify everything works: {{Cmd\|$ podman run --rm hello-world}}

	~~{{Cmd\|$ podman run --rm hello-world}}~~		== Troubleshooting ==

	==== Shared mount ====		=== Shared mount ===

	Containers on linux might require filesystems to be mounted with different propagation than the kernel default of 'private'. If you see a warning:		Containers on linux might require filesystems to be mounted with different propagation than the kernel default of 'private'. If you see a warning:
Line 41:		Line 39:
	: WARN[0000] "/" is not a shared mount, this could cause issues or missing mounts with rootless containers		: WARN[0000] "/" is not a shared mount, this could cause issues or missing mounts with rootless containers

	you might want to fix this temporarily, for currently running system:		you might want to fix this temporarily, for currently running system: {{Cmd\|# mount --make-rshared /}}

	{{Cmd\|# mount --make-rshared /}}

	~~and try the command that caused the warning again.~~

	~~Alternatively, you could use following~~ command:		Try the command that caused the warning again.

	~~{{Cmd\|# findmnt -o PROPAGATION /}}~~

			Alternatively, you could use following command: {{Cmd\|# findmnt -o PROPAGATION /}}
	which should print:		which should print:

	PROPAGATION		PROPAGATION
	shared		shared

	For a permanent fix (after a [https://github.com/OpenRC/openrc/pull/526 OpenRC PR#526] is released - in newer version than 0.54.2-r1), edit {{path\|/etc/fstab}}:		For a permanent fix (after a [https://github.com/OpenRC/openrc/pull/526 OpenRC PR#526] is released - in newer version than 0.54.2-r1), edit {{path\|/etc/fstab}}:{{cmd\|# $EDITOR /etc/fstab}}

	{{cmd\|# $EDITOR /etc/fstab}}

	Add <code>shared</code> option to the root partition:		Add <code>shared</code> option to the root partition:

	/dev/sda2 / ext4 rw,relatime,shared 0 1		/dev/sda2 / ext4 rw,relatime,shared 0 1

	and after a reboot test it out similarly as above.		and after a reboot test it out similarly as above.

	=== Docker compose ===		=== Docker compose ===

	~~Podman provides a drop-in replacement for docker compose.~~ The {{Pkg\|podman-compose}} package provides ~~this~~.		The {{Pkg\|podman-compose}} package from provides a drop-in replacement for docker compose. Each time a docker compose is used, a warning will remind that this is using podman under the hood. This warning can be squelched permanently by running: {{cmd\|# touch /etc/containers/nodocker}}

	Each time ~~that~~ docker compose is used, a warning will remind that this is using podman under the hood. This warning can be squelched permanently by running:

	{{cmd\|# touch /etc/containers/nodocker}}

	[[Category:Virtualization]]		[[Category:Virtualization]]

Fossdd: add if container use vfs driver

2024-08-24T19:47:41Z

add if container use vfs driver

← Older revision		Revision as of 19:47, 24 August 2024
Line 19:		Line 19:

	driver = "btrfs"		driver = "btrfs"

			If you're running inside a container, change the storage driver to <code>vfs</code>

	=== Running in rootless mode ===		=== Running in rootless mode ===