Failure in fetching the registry list via UI
Summary
When you navigate to the container registry in the UI, you're confronted with the following error:
Something went wrong while fetching the registry list
In the logs:
Completed 500 Internal Server Error in 2863ms (ActiveRecord: 5.4ms | Elasticsearch: 0.0ms)
NoMethodError (undefined method `map' for nil:NilClass):
lib/container_registry/tag.rb:97:in `block in layers'
...
There are no errors when listing via the API.
Steps to reproduce
(How one can reproduce the issue - this is very important)
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
The UI throws an error about fetching the registry list, and an 500 error: NoMethodError (undefined method `map' for nil:NilClass):
What is the expected correct behavior?
Show the registry lis
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
🛟 Workaround
You need to enable delete in docker registry.
You have to add the parameter delete: enabled: true in /etc/docker/registry/config.yml
More details in: https://github.com/distribution/distribution/blob/main/docs/configuration.md#delete