vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
cri-o/cmd/kpod
History
Nalin Dahyabhai 2e50006f1c Avoid using lower-level storage APIs 
Switch from using the lower-level storage APIs (accessing LayerStore,
ImageStore, and ContainerStore types directly) in favor of the
higher-level ones that take care of synchronization and locking for us.

Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
2017-07-25 13:29:49 -04:00
..
docker Implement kpod inspect 2017-07-21 08:11:27 -04:00
common.go move functions supporting images command to libkpod/image 2017-07-24 14:35:36 -04:00
common_test.go move image-related functions out of cmd/kpod/common.go and into libkpod/image 2017-07-24 14:34:55 -04:00
history.go move code supporting push, pull, and inspect to libkpod and libkpod/image 2017-07-24 14:35:36 -04:00
images.go move functions supporting images command to libkpod/image 2017-07-24 14:35:36 -04:00
info.go Avoid using lower-level storage APIs 2017-07-25 13:29:49 -04:00
inspect.go move code supporting push, pull, and inspect to libkpod and libkpod/image 2017-07-24 14:35:36 -04:00
main.go Implement kpod inspect 2017-07-21 08:11:27 -04:00
pull.go move PushImage and PullImage to libkpod/image 2017-07-24 14:35:36 -04:00
push.go move functions supporting images command to libkpod/image 2017-07-24 14:35:36 -04:00
README.md Rename ocid to crio. 2017-05-12 09:56:06 -04:00
rmi.go Avoid using lower-level storage APIs 2017-07-25 13:29:49 -04:00
tag.go move container-related functions out of kpod and into libkpod 2017-07-24 14:34:55 -04:00
version.go kpod: version should not fail 2017-07-10 17:02:13 -04:00

README.md

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

  1. List pods.
  2. Launch simple pods (that require no daemon support).
  3. Exec commands in a container in a pod.
  4. Launch additional containers in a pod.
  5. List images.
  6. Remove images not in use.
  7. Pull images.
  8. Check image size.
  9. Report pod disk resource usage.