-
Notifications
You must be signed in to change notification settings - Fork 61
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
Failed to authorize - gitea when pushing an image - failed to verify certificate #451
Comments
I did a test on my machine usign an fresh instancde of idpbuilder created using version 0.8.1 and cannot reproduce your issue
|
So what I shoyld do now, or how to debug why it is happening in my environment? |
Disable the TLS verification or add the gitea TLS certificate to docker: https://docs.docker.com/reference/cli/dockerd/ |
@cmoulliard, disable TLS, where in idpbuilder? |
No using docker as this is your docker CLI which is complaining |
You can get it easily if you using your browser or the secret:
|
Hi @cmoulliard I tried the following on the command line Thanks for your help |
You can define (see please docker cli documentation - https://docs.docker.com/reference/cli/docker/#options) the path to access a local cert file like also the parameter to enable/disable TLS verification I suggest also that you move to podman which better works than docker today ;-)
|
What is your environment, configuration, and command?
docker push gitea.cnoe.localtest.me:8443/giteaadmin/ubuntu:24.04
Ubuntu 24.04
What did you do and What did you see instead?
I created a new repo at gitea.cnoe.localtest.me:8443/giteaadmin/ubuntu
Additional Information. Logs.
docker push gitea.cnoe.localtest.me:8443/giteaadmin/ubuntu:24.04
The push refers to repository [gitea.cnoe.localtest.me:8443/giteaadmin/ubuntu]
ff65ddf9395b: Unavailable
failed to authorize: failed to fetch oauth token: Post "https://gitea.cnoe.localtest.me:8443/v2/token": tls: failed to verify certificate: x509: certificate signed by unknown authority
The text was updated successfully, but these errors were encountered: