Podman: Difference between revisions
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
Orchestrators are generally not compatible with each other(?) | 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. | |||
Revision as of 14:42, 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
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.