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
Not able to delete any image #301
Comments
Hi, thank you for using my project and submitting issues 😄 First of all you I see you are using Now if the tag you deleted is no longer present in the UI after clicking on the trash button, that means everything goes right with the UI project. The registry server garbage collector is a bit complicated, you can check their documentation. You may also add the option Did I miss something in your issue ? There were many subjects 😅 |
Hi, I use this docker registry UI and I have an issue...
Bug description
images can't be removed, even if I have all otions allowed in config and docker-compose
A clear and concise description of what the bug is.
How to Reproduce
I'm runnig registry in docker-compose and registry-ui in another docker-compose. connection is ok, I see all the repo. After click on trash button, it says it has be deleted by cmd " registry garbage-collect config.yml, so i do that, it says "XY blob is eligable to delete" , but nothing happens and no space was freed. (I deleted 5 images with 350Mb each)
from docker registry log:
registry-registry-1 | 192.168.48.1 - - [03/May/2023:11:26:43 +0000] "DELETE /v2/heappe_approval_system-api/manifests/sha256:499f4bc59418244911c42a6a232cf87574802f8dde4a8f02732aaffeee99b390 HTTP/1.1" 202 0 "http://registry.xy.tech/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36"
also strange is, that UI runs only in incognito tab in chrome, even after clear cache is not working in normal tab.
For UI bug, steps to reproduce the behavior:
My docker-compose file
My private docker registry configuration
config.yml
Expected behavior
df -h will show some more free space in
overlay 349G 288G 62G 83% /var/lib/docker/overlay2/03ad939bb1635f01c93d4463c923357c67386233c56bae202e8298d5e2658d
Screenshots
it allways says, that I have to set Access-Control-Allow-Origin: ['https://registry.xy:80'] but it is already
System information
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: