-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
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 Ok, so we need to let user know and also offer a way how to do it? |
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. |
@dgolovin ah, alright. thanks for explanation, let's keep the issue opened then until the fix is at place. |
@dgolovin So I tried to override the signatures locally, to have a workaround, but I am missing an authentication:
|
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. |
@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. |
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.
Some image can be pushed:
Others cannot:
See apocas/docker-modem#171 issue about
[object Object]
in error message.The text was updated successfully, but these errors were encountered: