Files
podman/cmd/podman
Matthew Heon da70c9db6f When location of c/storage root changes, set VolumePath
We want named volumes to be created in a subdirectory of the
c/storage graph root, the same as the libpod root directory is
now. As such, we need to adjust its location when the graph root
changes location.

Also, make a change to how we set the default. There's no need to
explicitly set it every time we initialize via an option - that
might conflict with WithStorageConfig setting it based on graph
root changes. Instead, just initialize it in the default config
like our other settings.

Signed-off-by: Matthew Heon <matthew.heon@pm.me>
2019-02-26 09:37:00 -05:00
..
2019-02-21 13:49:42 -07:00
2019-02-25 09:10:09 -06:00
2019-02-22 14:13:08 -06:00
2019-02-22 14:13:08 -06:00
2019-02-14 15:03:11 -05:00
2019-02-11 17:48:34 -06:00
2019-02-22 14:13:08 -06:00
2019-02-08 10:26:43 -06:00
2019-02-23 07:19:30 -05:00
2019-02-15 14:38:46 -05:00
2019-02-22 14:13:08 -06:00
2019-02-18 19:37:09 -05:00
2019-02-23 16:16:41 -05:00
2019-02-21 10:11:19 -06:00
2019-02-22 17:00:24 -06:00
2019-02-22 14:13:08 -06:00
2019-02-22 17:00:24 -06:00
2019-02-15 14:38:46 -05:00
2019-02-22 14:13:08 -06:00
2019-02-22 14:13:08 -06:00
2018-10-23 12:57:14 +02:00
2019-02-15 14:38:46 -05:00
2019-02-25 08:54:11 -06:00
2019-02-25 09:10:09 -06:00
2019-02-25 09:10:09 -06:00
2019-02-15 14:38:46 -05:00
2019-02-25 16:14:06 -06:00
2019-02-22 14:13:08 -06:00
2019-02-22 14:13:08 -06:00
2019-02-22 17:00:24 -06:00
2019-02-22 17:00:24 -06:00
2018-05-11 15:32:27 +00:00
2019-02-22 14:13:08 -06:00
2019-02-22 14:13:08 -06:00
2019-02-08 10:26:43 -06:00
2019-02-22 17:00:24 -06:00
2019-02-15 14:38:46 -05:00
2018-08-16 17:12:36 +00:00
2019-02-22 14:13:08 -06:00
2019-02-22 14:13:08 -06:00
2019-02-22 14:13:08 -06:00
2019-02-22 17:00:24 -06:00
2019-02-22 14:13:08 -06:00
2019-02-15 14:38:46 -05:00
2019-02-22 14:13:08 -06:00
2019-02-15 14:38:46 -05:00
2019-02-25 09:10:09 -06:00
2019-02-18 15:18:42 -05:00
2019-02-14 10:55:05 -06:00
2019-02-22 14:13:08 -06: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