libpod is a library used to create container pods.
Clone or download
Latest commit 579fc0f Jan 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.copr re-add BR for golang compiler to contrib/spec/podman.spec.in Oct 4, 2018
.github .github/ISSUE_TEMPLATE: Suggest '/kind bug' and '/kind feature' Jan 9, 2019
.tool Lint: Silence few given goconst lint warnings Nov 10, 2018
cmd/podman podman-remote inspect Jan 18, 2019
cni docs: fix contrib/cni broken link May 14, 2018
completions/bash Add --latest and --all to podman mount/umount Jan 16, 2019
contrib Run integrations test with remote-client Jan 14, 2019
docs Add --latest and --all to podman mount/umount Jan 16, 2019
hack Cirrus: Consolidate VM image names in once place Jan 17, 2019
libpod podman-remote inspect Jan 18, 2019
logo Touch up logo links May 15, 2018
pkg podman-remote inspect Jan 18, 2019
test podman-remote inspect Jan 18, 2019
utils Add container runlabel command Sep 28, 2018
vendor Merge pull request #2179 from rhatdan/vendor Jan 18, 2019
version Update master branch with v1.0 changes from 1.0 branch Jan 14, 2019
.cirrus.yml Cirrus: Consolidate VM image names in once place Jan 17, 2019
.gitignore Improve ps handling of container start/stop time Aug 8, 2018
.papr.sh Run integrations test with remote-client Jan 14, 2019
.papr.yml Cirrus: Migrate PAPR testing of F28 to Cirrus Dec 14, 2018
.papr_prepare.sh Move python code from contrib to it's own repo python-podman Jan 10, 2019
.ubuntu_prepare.sh Add ability for ubuntu to be tested Oct 3, 2018
API.md podman-remote inspect Jan 18, 2019
CONTRIBUTING.md [skip ci] Docs: Add Bot Interactions section Jan 4, 2019
Dockerfile Move python code from contrib to it's own repo python-podman Jan 10, 2019
Dockerfile.CentOS Move python code from contrib to it's own repo python-podman Jan 10, 2019
Dockerfile.Fedora Move python code from contrib to it's own repo python-podman Jan 10, 2019
LICENSE Initial commit Nov 1, 2017
Makefile Update README for v1.0.0 Jan 16, 2019
OWNERS Make list of approvers same as reviewers Nov 13, 2018
README.md Update README for v1.0.0 Jan 16, 2019
RELEASE_NOTES.md Update master branch with v1.0 changes from 1.0 branch Jan 14, 2019
Vagrantfile Enhancements to papr tests Nov 17, 2017
changelog.txt Update master branch with v1.0 changes from 1.0 branch Jan 14, 2019
code-of-conduct.md Initial checkin from CRI-O repo Nov 1, 2017
commands.md Merge pull request #1928 from baude/podtokube Dec 7, 2018
crio-umount.conf Initial checkin from CRI-O repo Nov 1, 2017
docker docker: Double quote array expansions to avoid re-splitting elements Oct 5, 2018
install.md Add openSUSE Kubic to install.md Jan 17, 2019
libpod.conf oci: allow to define multiple OCI runtimes Jan 14, 2019
seccomp.json update seccomp.json Nov 8, 2018
transfer.md Change references to cri-o to point at new repository Sep 7, 2018
troubleshooting.md Add local storage.conf example to troubleshoot Jan 14, 2019
vendor.conf Merge pull request #2179 from rhatdan/vendor Jan 18, 2019

README.md

PODMAN logo

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 podman tool, for managing Pods, Containers, and Container Images.

Overview and scope

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

  • Support multiple image formats including the existing Docker/OCI 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.

Roadmap

  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

  • Signing and pushing images to various image storages. See Skopeo.
  • Container Runtimes daemons for working with the Kubernetes CRI interface. See CRI-O.

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 podman.io 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.

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 GitHub.com with Buildah (GitHub) and Podman (GitHub). Both Buildah and Podman are command line tools that work on 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. Buildah’s goal is also to provide a lower level coreutils interface to build images, allowing people to build containers without requiring a Dockerfile. The intent with Buildah is to allow other scripting languages to build container images, without requiring a daemon.

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 cannot 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.