gitlab-ctl registry-garbage-collect will fail if registry_path is changed to other place
Summary
gitlab-ctl registry-garbage-collect
will fail if registry_path
is changed to other place
ok: down: registry: 0s, normally up
Running garbage-collect using configuration from /var/opt/gitlab/registry/config.yml, this might take a while...
failed to garbage collect: failed to mark: filesystem: Path not found: /docker/registry/v2/repositories
Failed to run garbage-collect command, starting registry service.
ok: run: registry: (pid 62056) 1s
Steps to reproduce
Change registry_path in /etc/gitlab/gitlab.rb
gitlab_rails['registry_path'] = "/home/var/opt/gitlab/gitlab-rails/shared/registry"
and run gitlab-ctl reconfigure
The rootdirectory
is not changed in /var/opt/gitlab/registry/config.yml
storage: {"filesystem":{"rootdirectory":"/var/opt/gitlab/gitlab-rails/shared/registry"},"cache":{"blobdescriptor":"inmemory"},"delete":{"enabled":true}}
gitlab-ctl registry-garbage-collect
will fail if registry_path
is changed to other place