cb0bb94c68
Avoid parsing metadata that the image library keeps in order to find an image's top layer and creation date; instead, use the values which the storage library now makes available, which will be correct once we merge PR #654 or something like it. Instead of assuming the last blob which was added for the image was the manifest, read it directly and compute its digest ourselves. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com> |
||
|---|---|---|
| .. | ||
| docker | ||
| common.go | ||
| common_test.go | ||
| history.go | ||
| images.go | ||
| info.go | ||
| inspect.go | ||
| main.go | ||
| pull.go | ||
| push.go | ||
| README.md | ||
| rmi.go | ||
| tag.go | ||
| version.go | ||
kpod - Simple debugging tool for pods and images
kpod is a simple client only tool to help with debugging issues when daemons such as CRI runtime and the kubelet are not responding or failing. A shared API layer could be created to share code between the daemon and kpod. kpod does not require any daemon running. kpod utilizes the same underlying components that crio uses i.e. containers/image, container/storage, oci-runtime-tool/generate, runc or any other OCI compatible runtime. kpod shares state with crio and so has the capability to debug pods/images created by crio.
Use cases
- List pods.
- Launch simple pods (that require no daemon support).
- Exec commands in a container in a pod.
- Launch additional containers in a pod.
- List images.
- Remove images not in use.
- Pull images.
- Check image size.
- Report pod disk resource usage.