-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manifest push
fails when following example
#18360
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
remote
Problem is in podman-remote
Comments
Looks like this needs to be fixed at both podman and buildah end, if no destination is given use source as the destination and use @containers/podman-maintainers @mtrmac WDYT ? See: https://docs.docker.com/engine/reference/commandline/manifest_push/ |
Yes it should match the behaviour from podman-push IMO. |
PR #18395 should close this. |
flouthoc
added a commit
to flouthoc/podman
that referenced
this issue
May 1, 2023
`manifest push <source>` must work as-is if `source` is actually a valid path and no destination is provided, `podman` must internally choose `source` as its `destination` just like `podman push` See: https://github.com/containers/podman/blob/main/cmd/podman/images/push.go#L161 Closes: containers#18360 Signed-off-by: Aditya R <[email protected]>
lyarwood
added a commit
to lyarwood/kubevirt
that referenced
this issue
May 23, 2023
publish-kubevirt-builder uses podman to build and publish the builder image. This change works around a known podman manifest push bug [1] by providing the destination until a now merged fix is released [2]. [1] containers/podman#18360 [2] containers/podman@bab4217 Signed-off-by: Lee Yarwood <[email protected]>
lyarwood
added a commit
to lyarwood/kubevirt
that referenced
this issue
May 23, 2023
publish-kubevirt-builder uses podman to build and publish the builder image. This change works around a known podman manifest push bug [1] by providing the destination until a now merged fix is released [2]. [1] containers/podman#18360 [2] containers/podman@bab4217 Signed-off-by: Lee Yarwood <[email protected]>
lyarwood
added a commit
to lyarwood/kubevirt
that referenced
this issue
May 23, 2023
publish-kubevirt-builder uses podman to build and publish the builder image. This change works around a known podman manifest push bug [1] by providing the destination until a now merged fix is released [2]. [1] containers/podman#18360 [2] containers/podman@bab4217 Signed-off-by: Lee Yarwood <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Aug 25, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
remote
Problem is in podman-remote
Issue Description
The example commands in
podman-manifest(1)
fail at the push step:Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
The text was updated successfully, but these errors were encountered: