Podman - Revision history

Hdridder at 12:50, 14 January 2026

2026-01-14T12:50:06Z

← Older revision		Revision as of 12:50, 14 January 2026
Line 43:		Line 43:
	;podman run --rm <image ID> <command>		;podman run --rm <image ID> <command>
	:Run <command> in the container, remove the container on exit,		:Run <command> in the container, remove the container on exit,
			;podman exec -it <containerid> <command>
			:Run <command> in a running container, -it is needed for interactive commands like bash
	;podman stop <containerID>		;podman stop <containerID>
	:Stop a container		:Stop a container

Hdridder at 10:12, 23 October 2025

2025-10-23T10:12:46Z

← Older revision		Revision as of 10:12, 23 October 2025
Line 34:		Line 34:
	:Return the whole image specification as json-string		:Return the whole image specification as json-string

	;<nowiki>podman run -v <hostdir>:<containerdir> -it <image ID> bash</nowiki>		;<nowiki>podman run -v <hostdir>:<containerdir> --rm -it <image ID> bash</nowiki>
	:Create the container and open a bash prompt in it (as root user). When leaving the shell the container is closed		:Create the container and open a bash prompt in it (as root user). When leaving the shell the container is closed
	:This way you can run any command in a container that only exists while the command is running.		:This way you can run any command in a container that only exists while the command is running.

Hdridder at 09:40, 23 October 2025

2025-10-23T09:40:28Z

← Older revision		Revision as of 09:40, 23 October 2025
Line 38:		Line 38:
	:This way you can run any command in a container that only exists while the command is running.		:This way you can run any command in a container that only exists while the command is running.
	:<hostdir> is mounted on <containerdir> which will be created automatically.		:<hostdir> is mounted on <containerdir> which will be created automatically.
	:NOTE: <hostdir> should not be ~~mounted~~ filesystem, the container has no access to that.		:NOTE: <hostdir> should not be a NFS filesystem, the container has no access to that.
	;podman run -it --network=host <image ID>		;podman run -it --network=host <image ID>
	:You will enter the container with the network settings (interface, hostname,...) from the host system. This enables mailing from the container.		:You will enter the container with the network settings (interface, hostname,...) from the host system. This enables mailing from the container.

Hdridder at 14:25, 6 September 2025

2025-09-06T14:25:51Z

← Older revision		Revision as of 14:25, 6 September 2025
Line 6:		Line 6:
	A containerfile defines what will be in the podman image, running the image will create a container.		A containerfile defines what will be in the podman image, running the image will create a container.

	~~Podamn~~ containterfiles have the same syntax as dockerfiles. The podman build command looks first for Containerfile and then for Dockerfile in the specified directory.		Podman containterfiles have the same syntax as dockerfiles. The podman build command looks first for Containerfile and then for Dockerfile in the specified directory.

	=Basics=		=Basics=

Hdridder at 13:09, 19 August 2025

2025-08-19T13:09:40Z

← Older revision		Revision as of 13:09, 19 August 2025
Line 43:		Line 43:
	;podman run --rm <image ID> <command>		;podman run --rm <image ID> <command>
	:Run <command> in the container, remove the container on exit,		:Run <command> in the container, remove the container on exit,
			;podman stop <containerID>
			:Stop a container
			;podman rm <containerID>
			:Remove a container
			;podman image rm <imageID>
			:Remove an image

	;podman ps -a		;podman ps -a

Hdridder at 15:26, 25 July 2025

2025-07-25T15:26:23Z

← Older revision		Revision as of 15:26, 25 July 2025
Line 56:		Line 56:

	==FROM==		==FROM==
	FROM: Specifies what is the base-image. Images are on a registry server like docker.io. You can use aliases like ubuntu or debian but that is not advised as you cannot be 100% sure where the images will be coming from. Therefor it is advised to user the full image path like docker.io/library/debian		;FROM <Imagelocation>
			:Specifies what is the base-image. Images are on a registry server like docker.io. You can use aliases like ubuntu or debian but that is not advised as you cannot be 100% sure where the images will be coming from. Therefor it is advised to user the full image path like docker.io/library/debian
	;podman search docker.io/library/nginx		;podman search docker.io/library/nginx
	:List all images for nginx		:List all images for nginx

	==RUN==		==RUN==
	Specify a command to run when the images is build. You can have a whole lot of these.		;RUN <command>
			:Specify a command to run when the images is build. You can have a whole lot of these.

	==CMD==		==CMD==
	Command to run when the container starts		;CMD <command>
			:Command to run when the container starts

	==LABEL==		==LABEL==
	~~Give the container a label, specify like <code>~~LABEL name="My Name"~~</code>~~. You can have several labels of a container.		;LABEL name="My Name"
			:Give the container a label. You can have several labels of a container.

			==COPY==
			;COPY <localfile> <containerpath>
			:Copy <localfile>, that must be in Containerfile directory, to <containerpath>

	=Full-fledged container=		=Full-fledged container=

Hdridder at 15:02, 25 July 2025

2025-07-25T15:02:37Z

← Older revision		Revision as of 15:02, 25 July 2025
Line 37:		Line 37:
	:Create the container and open a bash prompt in it (as root user). When leaving the shell the container is closed		:Create the container and open a bash prompt in it (as root user). When leaving the shell the container is closed
	:This way you can run any command in a container that only exists while the command is running.		:This way you can run any command in a container that only exists while the command is running.
	:<hostdir> is mounted on <containerdir> which will be created automatically		:<hostdir> is mounted on <containerdir> which will be created automatically.
	;podman run --rm <image ID>		:NOTE: <hostdir> should not be mounted filesystem, the container has no access to that.
	:~~Delete~~ the ~~image~~ on exit		;podman run -it --network=host <image ID>
			:You will enter the container with the network settings (interface, hostname,...) from the host system. This enables mailing from the container.
			;podman run --rm <image ID> <command>
			:Run <command> in the container, remove the container on exit,


Line 67:		Line 70:
	Give the container a label, specify like <code>LABEL name="My Name"</code>. You can have several labels of a container.		Give the container a label, specify like <code>LABEL name="My Name"</code>. You can have several labels of a container.

	=Full-fledged ~~interactive~~ container=		=Full-fledged container=

	==Containerfile==		==Containerfile==
Line 76:		Line 79:
	LABEL maintainer="Hans de Ridder"		LABEL maintainer="Hans de Ridder"
	RUN apt-get update		RUN apt-get update
	RUN apt-get -y install less joe vim		RUN apt-get -y install less joe vim exim4 procps
	RUN apt-get -y install python3-full		RUN apt-get -y install python3-full
	RUN python3 -m venv /opt/python/venv		RUN python3 -m venv /opt/python/venv
	ENV PATH="/opt/python/venv/bin:$PATH"		ENV PATH="/opt/python/venv/bin:$PATH"
	RUN pip install pandas		RUN pip install pandas
			COPY update-exim4.conf.conf /etc/exim4/
			RUN update-exim4.conf
	CMD ["bash", "-i"]		CMD ["bash", "-i"]
	</syntaxhighlight>		</syntaxhighlight>
Line 88:		Line 93:
	:Build the image		:Build the image
	;podman run -it --name FF <image ID>		;podman run -it --name FF <image ID>
	:You will enter the container		:You will enter the container.
	;podman start -ia FF		;podman start -ia FF
	:Re-enter the container after you left it. If the container is already running you will be in the same shell.		:Re-enter the container after you left it. If the container is already running you will be in the same shell.

	~~=Podman Virtual Machine=~~
	~~;apt install qemu-system~~
	~~:Install VM support~~

Hdridder at 12:30, 25 July 2025

2025-07-25T12:30:52Z

← Older revision		Revision as of 12:30, 25 July 2025
Line 91:		Line 91:
	;podman start -ia FF		;podman start -ia FF
	:Re-enter the container after you left it. If the container is already running you will be in the same shell.		:Re-enter the container after you left it. If the container is already running you will be in the same shell.

			=Podman Virtual Machine=
			;apt install qemu-system
			:Install VM support

Hdridder at 11:38, 25 July 2025

2025-07-25T11:38:17Z

← Older revision		Revision as of 11:38, 25 July 2025
Line 9:		Line 9:

	=Basics=		=Basics=
	;~~Installation:~~		;apt install podman
	apt install podman		:Install podman

	;This creates a working container with a python virtual environment		;This containerfile creates a working container with a python virtual environment
	~~:Containerfile~~
	<syntaxhighlight lang=text>		<syntaxhighlight lang=text>
	FROM debian		FROM debian
Line 66:		Line 65:

	==LABEL==		==LABEL==
	Give the container a label specify like <code>LABEL name="My Name"</code>. You can have several labels of a container.		Give the container a label, specify like <code>LABEL name="My Name"</code>. You can have several labels of a container.

	=Full-fledged interactive container=		=Full-fledged interactive container=
Line 72:		Line 71:
	==Containerfile==		==Containerfile==

	<syntaxhighlight ~~land~~=text>		<syntaxhighlight lang=text>
	FROM docker.io/library/debian		FROM docker.io/library/debian
	LABEL name="Full-fledged debian image"		LABEL name="Full-fledged debian image"
Line 87:		Line 86:
	==Usage==		==Usage==
	;podman build -t debian <directory>		;podman build -t debian <directory>
	;Build the image		:Build the image
	;podman run -it --name FF <image ID>		;podman run -it --name FF <image ID>
	:You will enter the container		:You will enter the container
	;podman start -ia FF		;podman start -ia FF
	:Re-enter the container after you left it.		:Re-enter the container after you left it. If the container is already running you will be in the same shell.

Hdridder: Created page with "Category:Linux/Unix Podman is used to create containers, like Docker. In a container system resources are separated from each other e.g. to create a development environment where the developer can experiment freely without the risk of jeopardizing the host system. The main difference is podman does not need a daemon like docker. It is lighter and more secure [https://www.geeksforgeeks.org/devops/podman-vs-docker/#podman-vs-docker-a-detailed-comparison] A contai..."

2025-07-25T11:00:21Z

Created page with "Category:Linux/Unix Podman is used to create containers, like Docker. In a container system resources are separated from each other e.g. to create a development environment where the developer can experiment freely without the risk of jeopardizing the host system. The main difference is podman does not need a daemon like docker. It is lighter and more secure [https://www.geeksforgeeks.org/devops/podman-vs-docker/#podman-vs-docker-a-detailed-comparison] A contai..."

New page

[[Category:Linux/Unix]]
Podman is used to create containers, like [[Docker]]. In a container system resources are separated from each other e.g. to create a development environment where the developer can experiment freely without the risk of jeopardizing the host system.

The main difference is podman does not need a daemon like docker. It is lighter and more secure [https://www.geeksforgeeks.org/devops/podman-vs-docker/#podman-vs-docker-a-detailed-comparison]

A containerfile defines what will be in the podman image, running the image will create a container.

Podamn containterfiles have the same syntax as dockerfiles. The podman build command looks first for Containerfile and then for Dockerfile in the specified directory.

=Basics=
;Installation:
apt install podman

;This creates a working container with a python virtual environment
:Containerfile
<syntaxhighlight lang=text>
FROM debian
LABEL name="Hans de Ridder"
RUN apt-get update
RUN apt-get -y install python3-full
RUN python3 -m venv /home/ubuntu/venv
ENV PATH="/home/ubuntu/venv/bin:$PATH"
RUN pip install pandas
CMD ["echo", "I'm alive"]
</syntaxhighlight>

;<nowiki>podman build -t <name>:<tag> <directory></nowiki>
:This builds the image with a name and a tag
;podman pull <registry image>
:Create an image from the registry image (see [[#FROM]])

;podman image ls
:List all existing images
;podman image inspect <image ID>
:Return the whole image specification as json-string

;<nowiki>podman run -v <hostdir>:<containerdir> -it <image ID> bash</nowiki>
:Create the container and open a bash prompt in it (as root user). When leaving the shell the container is closed
:This way you can run any command in a container that only exists while the command is running.
:<hostdir> is mounted on <containerdir> which will be created automatically
;podman run --rm <image ID>
:Delete the image on exit

;podman ps -a
:List all containers

;podman system prune
:Delete unused images and build caches
;podman system prune -a
:Delete unused images and all build caches

=Containerfile commands=

==FROM==
FROM: Specifies what is the base-image. Images are on a registry server like docker.io. You can use aliases like ubuntu or debian but that is not advised as you cannot be 100% sure where the images will be coming from. Therefor it is advised to user the full image path like docker.io/library/debian

;podman search docker.io/library/nginx
:List all images for nginx

==RUN==
Specify a command to run when the images is build. You can have a whole lot of these.

==CMD==
Command to run when the container starts

==LABEL==
Give the container a label specify like <code>LABEL name="My Name"</code>. You can have several labels of a container.

=Full-fledged interactive container=

==Containerfile==

<syntaxhighlight land=text>
FROM docker.io/library/debian
LABEL name="Full-fledged debian image"
LABEL maintainer="Hans de Ridder"
RUN apt-get update
RUN apt-get -y install less joe vim
RUN apt-get -y install python3-full
RUN python3 -m venv /opt/python/venv
ENV PATH="/opt/python/venv/bin:$PATH"
RUN pip install pandas
CMD ["bash", "-i"]
</syntaxhighlight>

==Usage==
;podman build -t debian <directory>
;Build the image
;podman run -it --name FF <image ID>
:You will enter the container
;podman start -ia FF
:Re-enter the container after you left it.