Files
baude 8f14f966be return all inspect info for varlink containerinspect
when obtaining the inspect information for a container through varlink, we need
to extract more container related information by parsing the data through the
method 'GetCtrInspectInfo' which was previously only in podman's main.

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

Closes: #866
Approved by: rhatdan
2018-06-01 08:37:55 +00:00
..
2018-04-26 19:14:44 +00:00
2018-05-25 08:45:15 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-05-25 08:45:15 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-03-16 14:35:07 +00:00
2018-05-02 16:55:31 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-05-21 19:26:56 +00:00
2018-04-26 19:14:44 +00:00
2018-05-10 08:53:28 +00:00
2018-05-11 15:32:27 +00:00
2018-05-03 17:31:33 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-05-25 08:45:15 +00:00
2018-05-21 19:26:56 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-04-26 19:14:44 +00:00
2018-05-22 13:50:10 +00:00
2018-04-23 14:29:45 +00:00
2018-04-26 19:14:44 +00:00

podman - Simple debugging tool for pods and images

podman is a daemonless container runtime for managing containers, pods, and container images. It is intended as a counterpart to CRI-O, to provide low-level debugging not available through the CRI interface used by Kubernetes. It can also act as a container runtime independent of CRI-O, creating and managing its own set of containers.

Use cases

  1. Create containers
  2. Start, stop, signal, attach to, and inspect existing containers
  3. Run new commands in existing containers
  4. Push and pull images
  5. List and inspect existing images
  6. Create new images by committing changes within a container
  7. Create pods
  8. Start, stop, signal, and inspect existing pods
  9. Populate pods with containers