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
Push is denied in automated build hooks #1611
Comments
Hi @vladgh , this issue should have been fixed ~8hrs ago. Are you continuing to see problems if you retry? |
Last time I tried was about 8 hours ago 😬 before going to bed. I can confirm it works now. Thanks for the very fast response. |
I am still facing a similar problem. I use TravisCI to build Docker images and push them to public docker hub repo. This can be observed in the Travis build log below. Each build job compiles one docker image tag and pushes it.
The same happens with the other images in the other build jobs. Any suggestions? |
If you are not using the Hub autobuilds this is a different issue. It does appear that you are not properly logged into your account if you are unable to push from your local machine. I would retry your |
Thx, this is what I just tried:
Second, I delete the repo I am trying to push to manually from the DockerHub webpage.
However, pushing the second image within the same shell session (without logout/login inbetween) fails:
I am running Docker on Windows 10 locally:
|
Sorry for the bother, I just resolved the issue myself. It would be helpful to add a more informative error message when the push fails because reaching the limit of private repos. |
I am currently using hooks in an automated build to pass parameters to the docker build command, and tag the resulting images. The feature is documented here: https://docs.docker.com/docker-cloud/builds/advanced/
However, all my builds are now failing at the
post_push
step, where thedocker push "${DOCKER_REPO}:${version}"
command fails with:Did anything change in the past few days with the way Docker Hub runs the build process?
The text was updated successfully, but these errors were encountered: