mirror of https://github.com/containers/podman.git
b028f6aa75
Podman Desktop [1] is looking into improving the user experience which requires to know the source of an image. Consider the user triggers an image pull and Podman Desktop wants to figure out whether the image name refers to a Red Hat registry, for instance, to prompt installing the RH auth extension. Since the input values of images may be a short name [2], Podman Desktop has no means to figure out the (potential) source of the image. Hence, add a new `/resolve` endpoint to allow external callers to figure out the (potential) fully-qualified image name of a given value. With the new endpoint, Podman Desktop can ask Podman directly to resolve the image name and then make an informed decision whether to prompt the user to perform certain tasks or not. This for sure can also be used for any other registry (e.g., Quay, Docker Hub). [1] https://github.com/containers/podman-desktop/issues/5771 [2] https://www.redhat.com/sysadmin/container-image-short-names Signed-off-by: Valentin Rothberg <vrothberg@redhat.com> |
||
|---|---|---|
| .. | ||
| containers.go | ||
| containers_create.go | ||
| containers_stats.go | ||
| generate.go | ||
| healthcheck.go | ||
| images.go | ||
| images_pull.go | ||
| images_push.go | ||
| info.go | ||
| kube.go | ||
| manifests.go | ||
| networks.go | ||
| play.go | ||
| pods.go | ||
| secrets.go | ||
| swagger_spec.go | ||
| system.go | ||
| volumes.go | ||