sameersbn
401 in container registry logs
Hello everyone. Maybe someone can help me with my situation. I am using sameersbn Gitlab 17.4.1. Some time ago i have realised that registry i have been using has grown to 1,5Tb an I can't delete any images from it using GitLab UI. So I dived in to the registry question an realised that third party registry is no supported anymore. I migrated to the official registry docker image and now I can delete images using GitLab UI and even use a cleanup functionality. So, at this moment I faced next problem. I am getting enormous amount of logs in registry container and all they are the same
{"content_type":"application/json","correlation_id":"01JKY0ZMDMP25HMMVS01X5ANNH","duration_ms":0,"host":"registry.examle.com","level":"info","method":"GET","msg":"access","proto":"HTTP/1.0","referrer":"","remote_addr":"172.24.0.1:35512","remote_ip":"111.111.111.111","status":401,"system":"http","time":"2025-02-12T21:28:02.740Z","ttfb_ms":0,"uri":"/v2/","user_agent":"docker/20.10.12 go/go1.16.12 git-commit/459d0df kernel/5.4.0-200-generic os/linux arch/amd64","written_bytes":87} {"config_http_addr":":5000","config_http_host":"","config_http_net":"","config_http_prefix":"","config_http_relative_urls":false,"correlation_id":"01JKY0ZSA27KYY6X742YEXKHXT","go_version":"go1.22.5","level":"info","method":"GET","msg":"router info","path":"/v2/","root_repo":"","router":"gorilla/mux","time":"2025-02-12T21:28:07.746Z","version":"v4.8.0-gitlab"}
*I have changed the remote_ip parametr in logs example As i understand 401 means that intensification don't feels well.
What can be the reson for this?
And one more question is... How I can clean my registry? 1,5Tb is not exemptible in my case. I feel that there are tons of artifacts, or things like that. P.S. I am not the guy how set un the system, but I have to deal with it now and actualy it is my first with GitLab system configuration/administration, so please be gentle. :)
Maybe related: https://gitlab.com/gitlab-org/gitlab/-/issues/22436#note_353744790
