Files
Giuseppe Scrivano 17b60891b6 rm: fix cleanup race
we fire the cleanup process asynchronously so we might race with a
command like: podman run --rm --name foo ... && podman run --rm --name foo

Fix it by ensuring the container is deleted before we exit.  This
will race with the "cleanup" process, but it is fine as one of the two
commands will fail with ErrNoSuchCtr while the other succeeds.

Closes: https://github.com/containers/libpod/issues/2619

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2019-03-13 20:26:56 +01:00
..
2019-03-11 09:28:57 +01:00
2019-02-11 17:48:34 -06:00
2019-03-12 14:29:18 -05:00
2019-03-13 10:22:10 -06:00
2019-03-12 14:29:18 -05:00
2018-05-11 15:32:27 +00:00
2019-03-13 20:26:56 +01:00
2018-08-16 17:12:36 +00:00
2019-03-12 16:29:54 -06:00
2019-02-25 09:10:09 -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