Creating a Podman glossary of the top 40 concepts, particularly sorted by their commonality of use, is an ambitious task due to the depth and breadth of Podman's features. Podman (Pod Manager) is a fully featured container engine that is a drop-in replacement for Docker. It offers a daemonless, open-source, Linux-native tool that facilitates developing, managing, and running OCI Containers on your Linux System. Podman operates containers without the need for a container daemon, which Docker requires, thus providing a more secure and efficient way to manage containers.
Given the space constraints and the complexity of detailing 40 concepts, I'll outline some of the top Podman concepts and their usage in a simplified MediaWiki format. This list isn't exhaustive but aims to cover foundational concepts and commonly used features in Podman.
Basic Podman Glossary
This glossary outlines the most commonly used Podman concepts, providing users with a foundational understanding of Podman's functionalities and how they are applied in container management.
Podman
A daemonless, open-source, Linux-native tool designed to make it easy to find, run, build, share and deploy applications using Open Containers Initiative (OCI) Containers and Container Images.
Container
An isolated environment that can run applications and their dependencies. Containers are created from images and can be managed using Podman commands.
Image
A static file that includes the executable code and libraries needed to run an application. Images serve as the basis for containers.
Pod
A group of one or more containers sharing the same network namespace, among other shared resources. Pods are a higher-level concept to bundle containers together.
Buildah
A tool that Podman integrates with to allow users to build container images from a Dockerfile or a custom script without requiring a full container runtime or daemon.
Skopeo
A command-line utility that performs various operations on container images and image repositories. Podman uses Skopeo for operations like inspecting images without pulling them.
Rootless Containers
Podman’s ability to run containers without requiring root privileges, enhancing the security by limiting the potential impact of a security breach within a container.
`podman run`
Command to run a container from an image. This is one of the most basic and commonly used Podman commands.
; Example
`podman ps`
Displays a list of running containers.
; Example
`podman images`
Lists the images available on the system.
; Example
`podman pull`
Pulls an image from a registry to the local machine.
; Example
`podman push`
Pushes an image from the local system to a registry.
; Example
`podman build`
Builds a container image from a Dockerfile.
; Example
`podman commit`
Creates a new image from a container's changes.
; Example
`podman login`
Logs into a container registry.
; Example
`podman logout`
Logs out of a container registry.
; Example
`podman pod`
Commands under `podman pod` manage groups of containers, or pods.
; Example
`podman stop`
Stops one or more running containers.
; Example
`podman start`
Starts one or more stopped containers.
; Example
`podman rm`
Removes one or more containers from the host.
; Example
`podman rmi`
Removes one or more images from the local storage.
; Example
Namespaces
Mechanisms for isolating groups of processes from each other so they cannot see or interact with processes in other namespaces.
Cgroups (Control Groups)
A Linux kernel feature that limits, accounts for, and isolates the resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes.
This glossary offers an introduction to the essential functionalities of Podman, focusing on container management. To explore all 40 concepts thoroughly, one should delve into Podman's official documentation and resources, which provide comprehensive details, advanced features, and best practices.