Files
podman/cmd/podman
baude ed1ea8dea1 rename pod when we have a name collision with a container
when podman generate kube runs, it names the pod based on the first
container it finds. the resulting yaml file is perfectly acceptable
in a kubernetes environment.  But when replaying the YAML file
with podman, we cannot have a container and pod with the same name.
therefore, we rename the pod if find a collision to name_pod.

Signed-off-by: baude <bbaude@redhat.com>
2019-02-26 12:13:12 -06: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-26 17:33:17 +01: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 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