Files
baude e97ca5bd38 podman ps json output use batched ops
The podman ps command for non-json targets has the ability to use a "batched" function
which limits the use of locks needed.  The collection of output for JSON should use
this too.

Signed-off-by: baude <bbaude@redhat.com>

Closes: #380
Approved by: rhatdan
2018-02-23 17:56:51 +00:00
..
2018-01-08 19:12:17 +00:00
2018-02-08 20:17:17 +00:00
2017-12-20 10:08:17 +00:00
2018-01-08 19:12:17 +00:00
2017-12-20 10:08:17 +00:00
2018-01-08 19:12:17 +00:00
2018-02-02 16:57:54 +00:00
2018-02-09 15:27:52 +00:00
2018-02-15 20:13:08 +00:00
2018-02-03 19:49:14 +00:00
2018-01-23 08:54:57 -06:00
2018-02-23 17:56:51 +00:00
2018-01-18 18:32:10 +00:00
2018-01-08 18:15:55 +00:00
2018-02-06 18:09:31 +00:00
2018-01-27 08:25:54 +00:00
2017-12-18 16:46:05 +00:00
2018-02-05 15:41:06 +00:00
2018-01-29 08:18:05 -05:00
2018-01-08 22:44:38 +00:00

podman - Simple debugging tool for pods and images

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 failing. A shared API layer could be created to share code between the daemon and podman. podman does not require any daemon running. podman 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. podman 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.