mirror of https://github.com/containers/podman.git
458ba5a8af
This started off as an attempt to make `podman stop` on a container started with `--rm` actually remove the container, instead of just cleaning it up and waiting for the cleanup process to finish the removal. In the process, I realized that `podman run --rmi` was rather broken. It was only done as part of the Podman CLI, not the cleanup process (meaning it only worked with attached containers) and the way it was wired meant that I was fairly confident that it wouldn't work if I did a `podman stop` on an attached container run with `--rmi`. I rewired it to use the same mechanism that `podman run --rm` uses, so it should be a lot more durable now, and I also wired it into `podman inspect` so you can tell that a container will remove its image. Tests have been added for the changes to `podman run --rmi`. No tests for `stop` on a `run --rm` container as that would be racy. Fixes #22852 Fixes RHEL-39513 Signed-off-by: Matt Heon <mheon@redhat.com> |
||
|---|---|---|
| .. | ||
| annotations.go | ||
| autoupdate.go | ||
| checkpoint_restore.go | ||
| config.go | ||
| container.go | ||
| container_inspect.go | ||
| containerstate.go | ||
| diff.go | ||
| errors.go | ||
| exec_codes.go | ||
| exit_code_propagation.go | ||
| fileinfo.go | ||
| healthchecks.go | ||
| info.go | ||
| mount.go | ||
| mount_freebsd.go | ||
| mount_linux.go | ||
| mount_unsupported.go | ||
| pod_inspect.go | ||
| podstate.go | ||
| runtime.go | ||
| sdnotify.go | ||
| version.go | ||
| volume_inspect.go | ||