Skip to content
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

An error occurred while pushing the image httpd-24 to Developer Sandbox cluster - Error: (HTTP code 500) server error - [object Object] #122

Open
odockal opened this issue May 27, 2024 · 8 comments
Labels
kind/bug 🐞 Something isn't working

Comments

@odockal
Copy link

odockal commented May 27, 2024

If I try to push some of the images I have locally (some from registry.redhat.io, some other from publicly accessible sources like registry.access.redhat.com), there is an error from dev sandbox.

An error occurred while pushing the image 'registry.access.redhat.com/ubi8/httpd-24:latest' to Developer Sandbox cluster 'dev-sandbox-context'. Error: (HTTP code 500) server error - [object Object]

Some image can be pushed:

docker.io/library/httpd:latest
quay.io/odockal/alpine-local
docker.io/library/alpine

Others cannot:

registry.redhat.io/rhel8/nginx-122:latest
registry.redhat.io/ubi8/httpd-24:latest
registry.access.redhat.com/ubi8/httpd-24:latest

See apocas/docker-modem#171 issue about [object Object] in error message.

@odockal odockal added the kind/bug 🐞 Something isn't working label May 27, 2024
@dgolovin
Copy link
Collaborator

Most likely yhe image is signed and you have to add option to push command to remove signature. The criptic error is on docker-modem side, they don't capture the error property of the exception. I have issue opened there with pull request.

Try to push from cli and you will see actual error.

@dgolovin
Copy link
Collaborator

podman push default-route-openshift-image-registry.apps.sandbox-m3.1530.p1.openshiftapps.com/nivologd-dev/httpd-24
Getting image source signatures
Checking if image destination supports signatures
Error: Copying this image would require changing layer representation, which we cannot do: "Would invalidate signatures"

@odockal
Copy link
Author

odockal commented May 29, 2024

@dgolovin Ok, so we need to let user know and also offer a way how to do it?

@dgolovin
Copy link
Collaborator

This message is coming from docker-modem see (apocas/docker-modem#171). Until it is fixed, we cannot even detect the error and let user know what to do.

@odockal
Copy link
Author

odockal commented May 30, 2024

@dgolovin ah, alright. thanks for explanation, let's keep the issue opened then until the fix is at place.

@odockal
Copy link
Author

odockal commented May 30, 2024

@dgolovin So I tried to override the signatures locally, to have a workaround, but I am missing an authentication:

podman push default-route-openshift-image-registry.apps.sandbox-m3.1530.p1.openshiftapps.com/odockal-dev/httpd-24 --remove-signatures
Error: trying to reuse blob sha256:ba181bba861a60bb8f268a6efe89e6421b78b3cfb8113585e2a4ebab6bc57f63 at destination: checking whether a blob sha256:ba181bba861a60bb8f268a6efe89e6421b78b3cfb8113585e2a4ebab6bc57f63 exists in default-route-openshift-image-registry.apps.sandbox-m3.1530.p1.openshiftapps.com/odockal-dev/httpd-24: authentication required

@dgolovin
Copy link
Collaborator

yes, to do it manually, you have to add registry default-route-openshift-image-registry.apps.sandbox-m3.1530.p1.openshiftapps.com/odockal-dev/httpd-24 using any user name and the same token used in sandbox connection.

@dgolovin
Copy link
Collaborator

@odockal another option is to use 'podman push' instead of dockerode when podman-desktop/podman-desktop#5990 is fixed. Detect the error and request user confirmation to use --remove-signatures option when pushing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug 🐞 Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants