opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-06-20 00:51:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update the README to reflect the libpod move

Browse Source 
We no longer have to dance around the fact that the repo is named
"libpod" which simplifies the opening a bit. Also, refresh our
scope section and to-do section a bit.

Signed-off-by: Matthew Heon <matthew.heon@pm.me>
This commit is contained in:
Matthew Heon
2020-07-20 10:56:12 -04:00
parent 17f9b80600
commit 1aa67b541d
1 changed files with 16 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
README.md
View File

@ -1,9 +1,9 @@
![PODMAN logo](logo/podman-logo-source.svg) ![PODMAN logo](logo/podman-logo-source.svg)
# Library and tool for running OCI-based containers in Pods # Podman: A tool for managing OCI containers and pods
Libpod provides a library for applications looking to use the Container Pod concept, Podman (the POD MANager) is a tool for managing containers and images, volumes mounted into those containers, and pods made from groups of containers.
popularized by Kubernetes. Libpod also contains the Pod Manager tool `(Podman)`. Podman manages pods, containers, container images, and container volumes. Podman is based on libpod, a library for container lifecycle management that is also contained in this repository. The libpod library provides APIs for managing containers, pods, container images, and volumes.
* [Latest Version: 2.0.2](https://github.com/containers/libpod/releases/latest) * [Latest Version: 2.0.2](https://github.com/containers/libpod/releases/latest)
* Latest Remote client for Windows * Latest Remote client for Windows
@ -15,26 +15,24 @@ popularized by Kubernetes. Libpod also contains the Pod Manager tool `(Podman)`
## Overview and scope ## Overview and scope
At a high level, the scope of libpod and Podman is the following: At a high level, the scope of Podman and libpod is the following:
* Support multiple image formats including the OCI and Docker image formats. * Support for multiple container image formats, including OCI and Docker images.
* Support for multiple means to download images including trust & image verification. * Full management of those images, including pulling from various sources (including trust and verification), creating (built via Containerfile or Dockerfile or committed from a container), and pushing to registries and other storage backends.
* Container image management (managing image layers, overlay filesystems, etc). * Full management of container lifecycle, including creation (both from an image and from an exploded root filesystem), running, checkpointing and restoring (via CRIU), and removal.
* Full management of container lifecycle. * Support for pods, groups of containers that share resources and are managed together.
* Support for pods to manage groups of containers together.
* Resource isolation of containers and pods. * Resource isolation of containers and pods.
* Support for a Docker-compatible CLI interface through Podman. * Support for a Docker-compatible CLI interface.
* Support for a REST API providing both a Docker-compatible interface and an improved interface exposing advanced Podman functionality. * Support for a REST API providing both a Docker-compatible interface and an improved interface exposing advanced Podman functionality.
* Integration with CRI-O to share containers and backend code. * In the future, integration with [CRI-O](https://github.com/cri-o/cri-o) to share containers and backend code.
Podman presently only supports running containers on Linux. However, we are building a remote client which can run on Windows and OS X and manage Podman containers on a Linux system via the REST API using SSH tunneling. Podman presently only supports running containers on Linux. However, we are building a remote client which can run on Windows and OS X and manage Podman containers on a Linux system via the REST API using SSH tunneling.
## Roadmap ## Roadmap
1. Complete the Podman REST API and Podman v2, which will be able to connect to remote Podman instances via this API 1. Further improvements to the REST API, with a focus on bugfixes and implementing missing functionality
1. Integrate libpod into CRI-O to replace its existing container management backend 1. Integrate libpod into [CRI-O](https://github.com/cri-o/cri-o) to replace its existing container management backend
1. Further work on the podman pod command 1. Improvements on rootless containers, with a focus on improving the user experience and exposing presently-unavailable features when possible
1. Further improvements on rootless containers
## Communications ## Communications
@ -67,10 +65,10 @@ A little configuration by an administrator is required before rootless Podman ca
## Out of scope ## Out of scope
* Specializing in signing and pushing images to various storage backends. * Specialized signing and pushing of images to various storage backends.
See [Skopeo](https://github.com/containers/skopeo/) for those tasks. See [Skopeo](https://github.com/containers/skopeo/) for those tasks.
* Container runtimes daemons for working with the Kubernetes CRI interface. * Support for the Kubernetes CRI interface for container management.
[CRI-O](https://github.com/cri-o/cri-o) specializes in that. The [CRI-O](https://github.com/cri-o/cri-o) daemon specializes in that.
* Supporting `docker-compose`. We believe that Kubernetes is the defacto * Supporting `docker-compose`. We believe that Kubernetes is the defacto
standard for composing Pods and for orchestrating containers, making standard for composing Pods and for orchestrating containers, making
Kubernetes YAML a defacto standard file format. Hence, Podman allows the Kubernetes YAML a defacto standard file format. Hence, Podman allows the