mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-10-11 00:17:41 +00:00
6589d75565
This started as a small fix to `podman inspect` where a container and image, with the same name/tag, were present, and `podman inspect` was run on that name. `podman inspect` in 1.9 (and `docker inspect`) will give you the container; in v2.0, we gave the image. This was an easy fix (just reorder how we check for image/container). Unfortunately, in the process of testing this fix, I determined that we regressed in a different area. When you run inspect on a number of containers, some of which do not exist, `podman inspect` should return an array of inspect results for the objects that exist, then print a number of errors, one for each object that could not be found. We were bailing after the first error, and not printing output for the containers that succeeded. (For reference, this applied to images as well). This required a much more substantial set of changes to properly handle - signatures for the inspect functions in ContainerEngine and ImageEngine, plus the implementations of these interfaces, plus the actual inspect frontend code needed to be adjusted to use this. Fixes #6556 Signed-off-by: Matthew Heon <matthew.heon@pm.me> |
||
|---|---|---|
| .. | ||
| annotations | ||
| api | ||
| auth | ||
| autoupdate | ||
| bindings | ||
| cgroups | ||
| channelwriter | ||
| checkpoint | ||
| criu | ||
| ctime | ||
| domain | ||
| env | ||
| errorhandling | ||
| hooks | ||
| inspect | ||
| kubeutils | ||
| lookup | ||
| namespaces | ||
| netns | ||
| network | ||
| parallel | ||
| ps | ||
| registrar | ||
| registries | ||
| resolvconf | ||
| rootless | ||
| rootlessport | ||
| seccomp | ||
| selinux | ||
| signal | ||
| spec | ||
| specgen | ||
| systemd | ||
| timetype | ||
| tracing | ||
| trust | ||
| util | ||
| varlink | ||
| varlinkapi | ||