cc1bad85fe
When using varlink to pull an image, we should expose the actual error to the caller. Signed-off-by: baude <bbaude@redhat.com> Closes: #744 Approved by: rhatdan |
||
|---|---|---|
| .copr | ||
| .github | ||
| .tool | ||
| cmd/podman | ||
| cni | ||
| completions/bash | ||
| contrib | ||
| docs | ||
| hack | ||
| libpod | ||
| logo | ||
| pkg | ||
| test | ||
| utils | ||
| vendor | ||
| version | ||
| .gitignore | ||
| .papr.sh | ||
| .papr.yml | ||
| .papr_prepare.sh | ||
| .travis.yml | ||
| API.md | ||
| changelog.txt | ||
| code-of-conduct.md | ||
| commands.md | ||
| CONTRIBUTING.md | ||
| crio-umount.conf | ||
| docker | ||
| Dockerfile | ||
| Dockerfile.CentOS | ||
| Dockerfile.Fedora | ||
| hooks.md | ||
| install.md | ||
| libpod.conf | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
| seccomp.json | ||
| transfer.md | ||
| Vagrantfile | ||
| vendor.conf | ||
libpod - library for running OCI-based containers in Pods
Status: Active Development
What is the scope of this project?
libpod provides a library for applications looking to use the Container Pod concept popularized by Kubernetes. libpod also contains a tool podman, which allows you to manage Pods, Containers, and Container Images.
At a high level, we expect the scope of libpod/podman to be 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).
- Container and POD process lifecycle management.
- Resource isolation of containers and PODS.
What is not in scope for this project?
- Building container images. See Buildah.
- Signing and pushing images to various image storages. See Skopeo.
- Container Runtimes daemons for working with Kubernetes CRIs. 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 runtime-spec implementation) and oci runtime tools
- Images: Image management using containers/image
- Storage: Storage and management of image layers using containers/storage
- Networking: Networking support through use of CNI
- Conmon: conmon Conmon is a tool for monitoring OCI runtimes. Part of the CRI-O package
Podman Information for Developers
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 Commands A list of the Podman commands with links to their man pages and in many cases videos showing the commands in use.
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.
Podman API Documentation on the Podman API using varlink.
Tutorials Tutorials on the Podman utility.
Contributing Information about contributing to this project.
Current Roadmap
- Basic pod/container lifecycle, basic image pull (done)
- Support for tty handling and state management (done)
- Basic integration with kubelet once client side changes are ready (done)
- Support for log management, networking integration using CNI, pluggable image/storage management (done)
- Support for exec/attach (done)