You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I use this docker registry UI and I have an issue.
Bug description
I am using the official docker registry docker image from dockerhub and connected the docker-registry-ui latest version from dockerhub to it. However, I am using Basic Auth on the docker registry.
While most of the HTTP requests from the docker registry UI to the docker registry work fine, the Basic Auth credentials are NOT included in HTTP requests with the OPTIONS method. However, the docker registry requires authentication even for the method OPTIONS and therefore, a 401 (unauthenticated) error is returned when I try to view the history of an image or when I try to delete an image.
How to Reproduce
For UI bug, steps to reproduce the behavior:
Enable Basic auth on docker registry
Try to delete an image from docker registry via docker registry UI while you are authenticated
Or try to view the history of an image via docker registry UI while you are authenticated
This is a known docker registry issue, and this is also described in the FAQ
Why DELETE fails with 401 status code (using Basic Auth) ?
This is caused by a bug in docker registry, I suggest to have your UI on the same domain than your registry and use NGINX_PROXY_PASS_URL e.g. registry.example.com/ui/. (see #104, #204, #207, #214).
Your choices are
Use NGINX_PROXY_PASS_URL
Configure your reverse proxy (traefik) to return 200 instead of 401 on OPTION methods
Hi, I use this docker registry UI and I have an issue.
Bug description
I am using the official docker registry docker image from dockerhub and connected the docker-registry-ui latest version from dockerhub to it. However, I am using Basic Auth on the docker registry.
While most of the HTTP requests from the docker registry UI to the docker registry work fine, the Basic Auth credentials are NOT included in HTTP requests with the OPTIONS method. However, the docker registry requires authentication even for the method OPTIONS and therefore, a 401 (unauthenticated) error is returned when I try to view the history of an image or when I try to delete an image.
How to Reproduce
For UI bug, steps to reproduce the behavior:
For service bug, steps to reproduce the behavior:
My docker-compose file
My private docker registry configuration
Expected behavior
I want to view the history and delete images via the docker registry UI without receiving 401 unauthenticated errors.
System information
The text was updated successfully, but these errors were encountered: