mirror of
https://github.com/containers/podman.git
synced 2025-06-29 06:57:13 +08:00
@ -23,23 +23,22 @@ At a high level, the scope of libpod and podman is the following:
|
||||
|
||||
## Roadmap
|
||||
|
||||
1. Python frontend for Varlink API
|
||||
1. Allow the Podman CLI to use a Varlink backend to connect to remote Podman instances
|
||||
1. Integrate libpod into CRI-O to replace its existing container management backend
|
||||
1. Further work on the podman pod command
|
||||
1. Further improvements on rootless containers
|
||||
1. In-memory locking to replace file locks
|
||||
|
||||
## Out of scope
|
||||
|
||||
* Signing and pushing images to various image storages.
|
||||
See [Skopeo](https://github.com/containers/skopeo/).
|
||||
* Container Runtimes daemons for working with Kubernetes CRIs.
|
||||
* Container Runtimes daemons for working with the Kubernetes CRI interface.
|
||||
See [CRI-O](https://github.com/kubernetes-sigs/cri-o).
|
||||
|
||||
## OCI Projects Plans
|
||||
|
||||
The plan is to use OCI projects and best of breed libraries for different aspects:
|
||||
- Runtime: [runc](https://github.com/opencontainers/runc) (or any OCI compliant runtime) and [oci runtime tools](https://github.com/opencontainers/runtime-tools) to generate the spec
|
||||
- Runtime: [runc](https://github.com/opencontainers/runc) (or any OCI compliant runtime) and [OCI runtime tools](https://github.com/opencontainers/runtime-tools) to generate the spec
|
||||
- Images: Image management using [containers/image](https://github.com/containers/image)
|
||||
- Storage: Container and image storage is managed by [containers/storage](https://github.com/containers/storage)
|
||||
- Networking: Networking support through use of [CNI](https://github.com/containernetworking/cni)
|
||||
|
Reference in New Issue
Block a user