Can't push when using frontend as registry
See original GitHub issueI have the frontend running on 80 and 443, proxying to the registry on 5000. When trying to push an image through the frontend to the registry, i get:
Error parsing HTTP response: invalid character '<' looking for beginning of value: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>403 Forbidden</title>\n</head><body>\n<h1>Forbidden</h1>\n<p>You don't have permission to access /v2/gitlab-ci/cloud-deploy/blobs/uploads/\non this server.<br />\n</p>\n<hr>\n<address>Apache/2.4.10 (Debian) Server at registry.magic-technik.de Port 80</address>\n</body></html>\n"
I’ve set the following EnvVars:
"ENV_DOCKER_REGISTRY_HOST=172.17.42.1",
"ENV_DOCKER_REGISTRY_PORT=5000",
"ENV_DOCKER_REGISTRY_USE_SSL=",
"ENV_REGISTRY_PROXY_FQDN=registry.example.com",
"ENV_REGISTRY_PROXY_PORT=443",
As a workaround i’m currently sending 80 to the frontend and 443 straight to the registry, but i’d like to use the frontend via HTTPS, too! 😉
Issue Analytics
- State:
- Created 8 years ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Cannot push/pull to remote docker registry - Stack Overflow
I currently have a working docker registry running on a debian server with a front end (https://github.com/kwk/docker-registry-frontend); both ...
Read more >Troubleshooting errors with Docker commands when using ...
An error indicating that the image can't be found is most often caused by either the image not existing in the upstream registry...
Read more >Docker push - Error - requested access to the resource is denied
Can someone help me with the following problem? First I logged in to Docker by executing the command: $ docker login.
Read more >Troubleshooting | Container Registry documentation
To fix access issues, ensure that you have the required permissions to push or pull. These permissions are listed in Permissions and roles....
Read more >Unable to push to swift storage backend - Launchpad Bugs
summary: - Unable to push to registry with swift storage backend + Unable to push to ... 2x Haproxy front-ends, 2x docker-registry backends....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve just encountered this issue for some strange reason. I pushed one image ok but then I tried to push another from a different server and I got this exact error message. After reading all of this I thought why not just proxy the registry commands straight through 😃 Here’s an nginx config that others might use for reference that works for us.
This is still an issue, however the fix is trivial and I’ve created a PR.
The current Apache config is already setup to proxy all /v2/ requests straight to the registry
However, the
FRONTEND_BROWSE_ONLY_MODE
config that @jangrewe mentioned is prohibiting pushes currently. @kwk - please see my pull request to fix this.@jc21 No need for nginx, just 3 more lines in the Apache config 😃