Files
Matthew Heon 831e2c30d4 Add ability to kill and stop containers
Also migrates kpod kill and kpod stop to libpod to use the new code

Fixes force removing containers, and actually deletes containers in runc when
removing them

Start is now capable of starting even when the container is unmounted

Signed-off-by: Matthew Heon <matthew.heon@gmail.com>

Closes: #68
Approved by: rhatdan
2017-11-29 12:15:15 +00:00
..
2017-11-01 11:24:59 -04:00
2017-11-01 11:24:59 -04:00
2017-11-28 15:01:20 +00:00
2017-11-02 15:30:39 -04:00
2017-11-27 14:46:45 -05:00
2017-11-07 19:16:31 +00:00
2017-11-02 15:30:39 -04:00
2017-11-02 15:30:39 -04:00
2017-11-02 15:30:39 -04:00
2017-11-02 15:30:39 -04:00
2017-11-02 15:30:39 -04:00
2017-11-09 17:36:11 +00:00
2017-11-28 14:47:35 +00:00
2017-11-02 15:30:39 -04:00
2017-11-02 15:30:39 -04:00
2017-11-01 11:24:59 -04:00
2017-11-02 15:30:39 -04:00
2017-11-27 16:46:06 +00:00
2017-11-14 16:46:26 +00:00
2017-11-28 15:01:20 +00:00
2017-11-07 19:16:31 +00:00
2017-11-02 15:30:39 -04:00
2017-11-02 15:30:39 -04:00
2017-11-01 14:19:19 -05:00
2017-11-01 11:24:59 -04:00
2017-11-27 19:05:59 +00:00

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.