|
1 | 1 | # podman - Simple debugging tool for pods and images |
2 | | -podman is a simple client only tool to help with debugging issues when daemons such as CRI runtime and the kubelet are not responding or |
3 | | -failing. A shared API layer could be created to share code between the daemon and podman. podman does not require any daemon running. podman |
4 | | -utilizes the same underlying components that crio uses i.e. containers/image, container/storage, oci-runtime-tool/generate, runc or |
5 | | -any other OCI compatible runtime. podman shares state with crio and so has the capability to debug pods/images created by crio. |
| 2 | +podman is a daemonless container runtime for managing containers, pods, and container images. |
| 3 | +It is intended as a counterpart to CRI-O, to provide low-level debugging not available through the CRI interface used by Kubernetes. |
| 4 | +It can also act as a container runtime independent of CRI-O, creating and managing its own set of containers. |
6 | 5 |
|
7 | 6 | ## Use cases |
8 | | -1. List pods. |
9 | | -2. Launch simple pods (that require no daemon support). |
10 | | -3. Exec commands in a container in a pod. |
11 | | -4. Launch additional containers in a pod. |
12 | | -5. List images. |
13 | | -6. Remove images not in use. |
14 | | -7. Pull images. |
15 | | -8. Check image size. |
16 | | -9. Report pod disk resource usage. |
| 7 | +1. Create containers |
| 8 | +2. Start, stop, signal, attach to, and inspect existing containers |
| 9 | +3. Run new commands in existing containers |
| 10 | +4. Push and pull images |
| 11 | +5. List and inspect existing images |
| 12 | +6. Create new images by committing changes within a container |
| 13 | +7. Create pods |
| 14 | +8. Start, stop, signal, and inspect existing pods |
| 15 | +9. Populate pods with containers |
0 commit comments