mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-10-18 11:57:32 +00:00
cf51c7ed9f
When doing a podman images, manifests lists look just like images, so it is logical that users would assume that they can just podman push them to a registry. The problem is we throw out weird errors when this happens and users need to somehow figure out this is a manifest list rather then an image, and frankly the user will not understand the difference. This PR will make podman push just do the right thing, by failing over and attempting to push the manifest if it fails to push the image. Fix up handling of manifest push Protocol should bring back a digest string, which can either be printed or stored in a file. We should not reimplement the manifest push setup code in the tunnel code but take advantage of the api path, to make sure remote and local work the same way. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com> |
||
|---|---|---|
| .. | ||
| reports | ||
| auto-update.go | ||
| container_ps.go | ||
| containers.go | ||
| engine.go | ||
| engine_container.go | ||
| engine_image.go | ||
| engine_system.go | ||
| events.go | ||
| filters.go | ||
| generate.go | ||
| healthcheck.go | ||
| images.go | ||
| manifest.go | ||
| network.go | ||
| play.go | ||
| pods.go | ||
| set.go | ||
| system.go | ||
| types.go | ||
| volumes.go | ||