Today I activate a new feature at work which provides the Container Registry feature on our GitLab instance.
However not all projects are requiring this feature, actually at the moment just a few. Therefore we wanted this option to be disabled by defaults and to the responsibility of the project leaders to activate or not when needed.
GitLab offers to disable the Container registryfeature for new projects only. What I wanted was to do that for existing projects. This needs to be done directly on the database, so back it up before doing this, and try it on a non-production environment first. Note that this was tested on GitLab 8.17.3 using PostreSQL 9.6, with other releases this could be different. In addition, the following is provided as is without any warranty, it worked for me, it might not for you and I’m in no way responsible if you mess your database.
Now that you have done your backup, to perform the changes on the database, you need to login as the `gitlab-psql` user:
When using Docker:
$ docker exec -it --user=gitlab-psql gitlab bash
When using omnibus package:
$ su - gitlab-psql
The following applies for both Docker and Omnibus installation once logged in:
$ export PGHOST="/var/opt/gitlab/postgresql" $ psql gitlabhq_production gitlabhq_production=# update projects SET container_registry_enabled = FALSE;