Podman: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
* Containers can continue running when Podman is stopped | * Containers can continue running when Podman is stopped | ||
* Upgrading Podman doesn't stop all containers (unlike upgrading Docker) | * Upgrading Podman doesn't stop all containers (unlike upgrading Docker) | ||
== Traps for the unwary == | |||
* Installing the podman package on Ubuntu doesn't include compose - you have to install podman-compose as well | |||
== Container orchestrators == | == Container orchestrators == | ||
Revision as of 15:15, 28 August 2025
Podman is an alternative to Docker for running containers on Linux. It is similar to Docker in many respects, but differs in some key areas:
- Doesn't require root privileges by default
- Containers can continue running when Podman is stopped
- Upgrading Podman doesn't stop all containers (unlike upgrading Docker)
Traps for the unwary
- Installing the podman package on Ubuntu doesn't include compose - you have to install podman-compose as well
Container orchestrators
A container orchestrator performs orchestration, i.e. the management of containers across nodes (which may be across different machines). For example, if you have two web nodes (with a load balancer) and a database node, your orchestrator will ensure that all the nodes are configured and can talk to each other as needed.
Orchestrators include:
- Kubernetes
- Apache Mesos
- Docker Swarm
Orchestrators are generally not compatible with each other(?)
Container engines
A container engine configures applications to run on nodes. These are what you will typically interact with during development.
Engines include:
- Docker
- Podman
Container runtimes
A container runtime is the interface between the kernel and the containerised application. A container engine will usually support multiple container runtimes.