Podman - Revision history

Arch is the best: virtualisation.containers.enable seems unnecessary

2026-08-15T20:24:01Z

virtualisation.containers.enable seems unnecessary

← Older revision		Revision as of 20:24, 15 August 2026
Line 2:		Line 2:

	== Setup ==		== Setup ==
	{{File\|3=virtualisation = {		{{File\|3=virtualisation.podman = {
	~~containers.~~enable = true;		enable = true;
	~~podman = {~~		dockerCompat = true; # Creates a symlink from docker to podman
	~~enable = true;~~		defaultNetwork.settings.dns_enabled = true; # Required for containers under podman-compose to be able to talk to each other.
	dockerCompat = true;
	defaultNetwork.settings.dns_enabled = true; # Required for containers under podman-compose to be able to talk to each other.
	};
	};		};

Giantdwarf: Updated podman compose documentation. I essentially copied the official documentation from https://docs.podman.io/en/stable/markdown/podman-compose.1.html and modified the instructions to use nixos options instead of manual file edits.

2026-07-07T19:31:57Z

Updated podman compose documentation. I essentially copied the official documentation from https://docs.podman.io/en/stable/markdown/podman-compose.1.html and modified the instructions to use nixos options instead of manual file edits.

@@ Line 23: / Line 23: @@
 == Tips and tricks ==
-=== podman-compose ===
+=== '''podman compose''' ===
-<code>podman-compose</code> is a drop-in replacement for <code>docker-compose</code>
+podman compose is a thin wrapper around an external compose provider such as [https://github.com/docker/compose docker-compose] or [https://github.com/containers/podman-compose podman-compose].  This means that <code>podman compose</code> is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well as the command and argument are passed directly to the compose provider.
-See [https://docs.podman.io/en/stable/markdown/podman-compose.1.html the official documentation]
+The default compose providers are <code>docker-compose</code> and <code>podman-compose</code>.  If installed, <code>docker-compose</code> takes precedence since it is the original implementation of the Compose specification.
 === With ZFS ===

Marie: Add podman group = root security warning

2026-07-01T15:01:46Z

Add podman group = root security warning

← Older revision		Revision as of 15:01, 1 July 2026
Line 16:		Line 16:
	];		];
	};\|name=/etc/nixos/configuration.nix\|lang=nix}}		};\|name=/etc/nixos/configuration.nix\|lang=nix}}

			{{Security Warning\|Beware that the podman group membership is effectively equivalent to being root, just like with Docker! <br> Consider using rootless podman.}}

	A reboot or re-login might be required for the permissions to take effect after applying changes		A reboot or re-login might be required for the permissions to take effect after applying changes

Infgotoinf: Add missing ;

2026-05-21T07:15:41Z

Add missing ;

← Older revision		Revision as of 07:15, 21 May 2026
Line 15:		Line 15:
	"podman"		"podman"
	];		];
	}\|name=/etc/nixos/configuration.nix\|lang=nix}}		};\|name=/etc/nixos/configuration.nix\|lang=nix}}
	A reboot or re-login might be required for the permissions to take effect after applying changes		A reboot or re-login might be required for the permissions to take effect after applying changes

Staticdev: The way to change registries globally caused conflicts and does not work.

2026-02-07T06:49:09Z

The way to change registries globally caused conflicts and does not work.

← Older revision		Revision as of 06:49, 7 February 2026
Line 120:		Line 120:
	To avoid this issue, you might restrict its registries configuration.		To avoid this issue, you might restrict its registries configuration.

	You can ~~do such using [~~[~~Home Manager]~~] ~~manually:~~		You can change the global registries with:<syntaxhighlight lang="nix">
			virtualisation.containers.registries.search = [ "docker.io" ];
			</syntaxhighlight>

	~~{{File\|3=# Global `/etc/containers/~~registries~~.conf`~~		For user-scoped registries you can do using [[Home Manager]] manually:
	~~environment.etc."containers/registries.conf".text = ''~~
	[~~registries.search~~]
	~~registries = ['docker.io'~~]
	~~'';~~

	# User-scoped `~/.config/containers/registries`		{{File\|3=# User-scoped `~/.config/containers/registries`
	xdg.configFile."containers/registries.conf".text = ''		xdg.configFile."containers/registries.conf".text = ''
	[registries.search]		[registries.search]

Malix: enhance: headers

2025-10-01T15:39:49Z

enhance: headers

← Older revision		Revision as of 15:39, 1 October 2025
Line 25:		Line 25:
	See [https://docs.podman.io/en/stable/markdown/podman-compose.1.html the official documentation]		See [https://docs.podman.io/en/stable/markdown/podman-compose.1.html the official documentation]

	=== ~~Using podman with~~ ZFS ===		=== With ZFS ===

	Rootless can't use [[ZFS]] directly but the overlay needs POSIX ACL enabled for the underlying ZFS filesystem, ie., <code>acltype=posixacl</code>		Rootless can't use [[ZFS]] directly but the overlay needs POSIX ACL enabled for the underlying ZFS filesystem, ie., <code>acltype=posixacl</code>
Line 31:		Line 31:
	Best to mount a dataset under <code>/var/lib/containers/storage</code> with property <code>acltype=posixacl</code>.		Best to mount a dataset under <code>/var/lib/containers/storage</code> with property <code>acltype=posixacl</code>.

	=== ~~Use Podman within~~ nix-shell ===		=== Within nix-shell ===
	From https://gist.github.com/adisbladis/187204cb772800489ee3dac4acdd9947 :<blockquote>{{File\|3={ pkgs ? import <nixpkgs> {} }:		From https://gist.github.com/adisbladis/187204cb772800489ee3dac4acdd9947 :<blockquote>{{File\|3={ pkgs ? import <nixpkgs> {} }:

Line 89:		Line 89:
	}\|name=podman-shell.nix\|lang=nix}}</blockquote>Note that rootless podman requires newuidmap (from shadow). If you're not on NixOS, this cannot be supplied by the Nix package 'shadow' since [https://nixos.org/manual/nix/unstable/expressions/derivations.html setuid/setgid programs are not currently supported by Nix].		}\|name=podman-shell.nix\|lang=nix}}</blockquote>Note that rootless podman requires newuidmap (from shadow). If you're not on NixOS, this cannot be supplied by the Nix package 'shadow' since [https://nixos.org/manual/nix/unstable/expressions/derivations.html setuid/setgid programs are not currently supported by Nix].

	=== ~~Run Podman containers~~ as systemd services ===		=== Containers as systemd services ===
	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
	{		{
Line 103:		Line 103:
	</syntaxHighlight>		</syntaxHighlight>

	=== ~~Run cross~~-architecture containers ~~with~~ binfmt/qemu ===		=== Cross-architecture containers using binfmt/qemu ===
	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
	boot.binfmt = {		boot.binfmt = {
Line 115:		Line 115:
	</syntaxhighlight>		</syntaxhighlight>

	=== ~~DevContainer~~ ===		=== DevContainers ===
	Using Podman, it is possible that the process of creation of DevContainers' containers to become stuck at the "Please select an image URL" step.		Using Podman, it is possible that the process of creation of DevContainers' containers to become stuck at the "Please select an image URL" step.

Malix: general enhancements

2025-10-01T15:38:06Z

general enhancements

Show changes

Jonniecache: /* Run cross architecture containers with binfmt/qemu */

2025-02-22T18:37:10Z

Run cross architecture containers with binfmt/qemu

← Older revision		Revision as of 18:37, 22 February 2025
Line 51:		Line 51:
	</syntaxHighlight>		</syntaxHighlight>

	=== Run cross architecture containers with binfmt/qemu ===		=== Run cross-architecture containers with binfmt/qemu ===
	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
	boot.binfmt = {		boot.binfmt = {

Jonniecache: /* Tips and tricks */

2025-02-22T18:32:59Z

Tips and tricks

← Older revision		Revision as of 18:32, 22 February 2025
Line 63:		Line 63:
	</syntaxHighlight>		</syntaxHighlight>

	~~'''~~DevContainer~~'''~~		=== DevContainer ===

	To use DevContainer with Podman, it is possible that the process of creation of containers is stuck a `Please select an image URL`.		To use DevContainer with Podman, it is possible that the process of creation of containers is stuck a `Please select an image URL`.

Drupol at 18:38, 21 February 2025

2025-02-21T18:38:40Z

@@ Line 61: / Line 61: @@
 $ podman run --arch arm64 'docker.io/alpine:latest' arch
 aarch64
 </syntaxHighlight>