Skip to content
libpod is a library used to create container pods. Home of Podman.
Branch: master
Clone or download
openshift-merge-robot Merge pull request #2703 from edsantiago/bats
BATS: new tests, and improvements to existing ones
Latest commit 537c382 Mar 19, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.copr re-add BR for golang compiler to contrib/spec/ Oct 4, 2018
.github issue template: run `podman info --debug` Feb 25, 2019
cni docs: fix contrib/cni broken link May 14, 2018
completions Merge pull request #2595 from jwhonce/bug/1677908 Mar 15, 2019
contrib Enable rootless integration tests Mar 19, 2019
libpod ps: fix segfault if the store is not initialized Mar 19, 2019
logo Touch up logo links May 15, 2018
pkg Export ConmonPidFile in 'podman inspect' for containers Mar 18, 2019
test Merge pull request #2703 from edsantiago/bats Mar 19, 2019
utils Corrected detach man pages and code comments Mar 13, 2019
vendor Vendor docker/docker, fsouza and more #2 Mar 13, 2019
.cirrus.yml Enable rootless integration tests Mar 19, 2019
.gitignore Run integrations test with remote-client Jan 14, 2019
.papr.yml Cirrus: Migrate PAPR testing of F28 to Cirrus Dec 14, 2018 Move python code from contrib to it's own repo python-podman Jan 10, 2019 Add event logging to libpod, even display to podman Mar 11, 2019 [ci skip] Critical note about merge bot Feb 28, 2019
Dockerfile.Fedora Replace skopeo-containers with containers-common Mar 14, 2019
LICENSE Initial commit Nov 1, 2017
Makefile zsh completion Mar 13, 2019
Vagrantfile Enhancements to papr tests Nov 17, 2017
changelog.txt Bump to v1.1.2 Mar 5, 2019 Cleanup messages on podman load Mar 18, 2019
libpod.conf Add volume path to default libpod.conf (and manpage) Feb 26, 2019 podman remote-client readme Feb 26, 2019
seccomp.json update seccomp.json Nov 8, 2018 Replace skopeo-containers with containers-common Mar 14, 2019


Library and tool for running OCI-based containers in Pods

Libpod provides a library for applications looking to use the Container Pod concept, popularized by Kubernetes. Libpod also contains the Pod Manager tool (Podman). Podman manages pods, containers, container images, and container volumes.

Overview and scope

At a high level, the scope of libpod and podman is the following:

  • Support multiple image formats including the OCI and Docker image formats.
  • Support for multiple means to download images including trust & image verification.
  • Container image management (managing image layers, overlay filesystems, etc).
  • Full management of container lifecycle
  • Support for pods to manage groups of containers together
  • Resource isolation of containers and pods.
  • Integration with CRI-O to share containers and backend code.

This project tests all builds against each supported version of Fedora, the latest released version of Red Hat Enterprise Linux, and the latest Ubuntu Long Term Support release. The community has also reported success with other Linux flavors.


  1. Allow the Podman CLI to use a Varlink backend to connect to remote Podman instances
  2. Integrate libpod into CRI-O to replace its existing container management backend
  3. Further work on the podman pod command
  4. Further improvements on rootless containers

Out of scope

  • Specializing in signing and pushing images to various storage backends. See Skopeo for those tasks.
  • Container runtimes daemons for working with the Kubernetes CRI interface. CRI-O specializes in that.
  • Supporting docker-compose. We believe that Kubernetes is the defacto standard for composing Pods and for orchestrating containers, making Kubernetes YAML a defacto standard file format. Hence, Podman allows the creation and execution of Pods from a Kubernetes YAML file (see podman-play-kube). Podman can also generate Kubernetes YAML based on a container or Pod (see podman-generate-kube), which allows for an easy transition from a local development environment to a production Kubernetes cluster.

OCI Projects Plans

The plan is to use OCI projects and best of breed libraries for different aspects:

  • Runtime: runc (or any OCI compliant runtime) and OCI runtime tools to generate the spec
  • Images: Image management using containers/image
  • Storage: Container and image storage is managed by containers/storage
  • Networking: Networking support through use of CNI
  • Builds: Builds are supported via Buildah.
  • Conmon: Conmon is a tool for monitoring OCI runtimes. It is part of the CRI-O package

Podman Information for Developers

For blogs, release announcements and more, please checkout the website!

Installation notes Information on how to install Podman in your environment.

OCI Hooks Support Information on how Podman configures OCI Hooks to run when launching a container.

Podman API Documentation on the Podman API using Varlink.

Podman Commands A list of the Podman commands with links to their man pages and in many cases videos showing the commands in use.

Podman Troubleshooting Guide A list of common issues and solutions for Podman.

Podman Usage Transfer Useful information for ops and dev transfer as it relates to infrastructure that utilizes Podman. This page includes tables showing Docker commands and their Podman equivalent commands.

Tutorials Tutorials on using Podman.

Remote Client A brief how-to on using the Podman remote-client.

Release Notes Release notes for recent Podman versions

Contributing Information about contributing to this project.

Buildah and Podman relationship

Buildah and Podman are two complementary open-source projects that are available on most Linux platforms and both projects reside at with Buildah here and Podman here. Both, Buildah and Podman are command line tools that work on Open Container Initiative (OCI) images and containers. The two projects differentiate in their specialization.

Buildah specializes in building OCI images. Buildah's commands replicate all of the commands that are found in a Dockerfile. This allows building images with and without Dockerfiles while not requiring any root privileges. Buildah’s ultimate goal is to provide a lower-level coreutils interface to build images. The flexibility of building images without Dockerfiles allows for the integration of other scripting languages into the build process. Buildah follows a simple fork-exec model and does not run as a daemon but it is based on a comprehensive API in golang, which can be vendored into other tools.

Podman specializes in all of the commands and functions that help you to maintain and modify OCI images, such as pulling and tagging. It also allows you to create, run, and maintain those containers created from those images.

A major difference between Podman and Buildah is their concept of a container. Podman allows users to create "traditional containers" where the intent of these containers is to be long lived. While Buildah containers are really just created to allow content to be added back to the container image. An easy way to think of it is the buildah run command emulates the RUN command in a Dockerfile while the podman run command emulates the docker run command in functionality. Because of this and their underlying storage differences, you can not see Podman containers from within Buildah or vice versa.

In short, Buildah is an efficient way to create OCI images while Podman allows you to manage and maintain those images and containers in a production environment using familiar container cli commands. For more details, see the Container Tools Guide.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.