Completely wipe container registry on S3 Minio backend

How to Use GitLab Self-managed
1

Problem to solve

I use a Minio-based S3 backend for the docker registry of my self-deployed Omnibus instance. I still did not migrate to the new Postgres metadata database. Since some time something must have been badly screwed, since I’m experiencing several problems with the registry (Docker registry troubles). For this reason I decided to completely wipe out the registry, migrate to the new metadata database, and see if in this way I can fix my issues. I’d need to understand how to perform the wipe: can I simply delete everything in the S3 bucket hosting the registry and restart Gitlab, or do I have to perform a more fine-grained delete? Is there any other cleanup operation I should perform?

Configuration

From /etc/gitlab/gitlab/rb:

registry['storage'] = {
  's3' => {
    'accesskey' => 'XXXXX,
    'secretkey' => 'YYYYY,
    'bucket' => 'gitlab-registry',
    'region' => 'eu-central-1',
    'regionendpoint' => 'https://my.minio.instance',
    'path_style' => true
  }
}

Versions

Self-managed

Versions

  • GitLab (Web: /help or self-managed system information sudo gitlab-rake gitlab:env:info): 17.5.0