vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
cri-o/cmd/kpod
History
umohnani8 b4d3b560d3 Changed debug flag to log-level in kpod/main.go 
The change in flag from debug to log-level was causing cri-o to fail when started
There was a reference to the debug flag in kpod/main.go that had not been changed

Signed-off-by: umohnani8 <umohnani@redhat.com>
2017-10-10 14:55:14 -04:00
..
docker Implement kpod inspect 2017-07-21 08:11:27 -04:00
formats Merge pull request #776 from umohnani8/kpod_ps 2017-08-23 07:08:31 -04:00
common.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
common_test.go server: add inspect unit test 2017-09-17 10:19:29 +02:00
diff.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
export.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
history.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
images.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
info.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
inspect.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
kill.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
load.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
logs.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
main.go Changed debug flag to log-level in kpod/main.go 2017-10-10 14:55:14 -04:00
mount.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
pause.go Add kpod pause and kpod unpause 2017-09-26 08:38:07 -04:00
ps.go Merge pull request #959 from rhatdan/validate 2017-10-04 18:29:57 -04:00
pull.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
push.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
README.md Rename ocid to crio. 2017-05-12 09:56:06 -04:00
rename.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
rm.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
rmi.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
save.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
stats.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
stop.go validateFlags command line options to make sure the user entered a value 2017-10-04 09:36:29 +00:00
tag.go Switch kpod load/push/save to use libpod runtime 2017-09-27 22:33:20 -04:00
umount.go Add kpod-mount and kpod-umount to mount and umount container images 2017-08-08 15:46:50 -04:00
unpause.go Add kpod pause and kpod unpause 2017-09-26 08:38:07 -04:00
version.go Update kpod version and info to show beta version 2017-09-10 12:17:43 -04:00
wait.go Add kpod wait 2017-09-27 09:03:33 -05: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.