We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I use this docker registry UI and I have an issue...
So I have a docker registry with this config:
docker-registry: container_name: docker-registry image: registry:latest restart: unless-stopped environment: REGISTRY_HTTP_HEADERS_Access-Control-Allow-Origin: '[https://mydomain.com]' REGISTRY_HTTP_HEADERS_Access-Control-Allow-Methods: '[HEAD,GET,OPTIONS,DELETE]' REGISTRY_HTTP_HEADERS_Access-Control-Allow-Credentials: '[true]' REGISTRY_HTTP_HEADERS_Access-Control-Allow-Headers: '[Authorization,Accept,Cache-Control]' REGISTRY_HTTP_HEADERS_Access-Control-Expose-Headers: '[Docker-Content-Digest]'
however when I try to go to the url:
However I can see the header inresponse:
The text was updated successfully, but these errors were encountered:
Hi, thank you for using my project.
Can I have messages from your browser console ?
Sorry, something went wrong.
No branches or pull requests
Hi, I use this docker registry UI and I have an issue...
So I have a docker registry with this config:
docker-registry:
container_name: docker-registry
image: registry:latest
restart: unless-stopped
environment:
REGISTRY_HTTP_HEADERS_Access-Control-Allow-Origin: '[https://mydomain.com]'
REGISTRY_HTTP_HEADERS_Access-Control-Allow-Methods: '[HEAD,GET,OPTIONS,DELETE]'
REGISTRY_HTTP_HEADERS_Access-Control-Allow-Credentials: '[true]'
REGISTRY_HTTP_HEADERS_Access-Control-Allow-Headers: '[Authorization,Accept,Cache-Control]'
REGISTRY_HTTP_HEADERS_Access-Control-Expose-Headers: '[Docker-Content-Digest]'
however when I try to go to the url:
However I can see the header inresponse:
The text was updated successfully, but these errors were encountered: