Registry creates backup of local repository on every update

Overview

If the registry service is enabled, every time the user runs gdk update, the container-registry folder will be moved to the .backups folder and a new container-registry folder will be cloned.

This can lead to the backups folder, which should ideally only create config files or small data files, increasing in size to 5 GB (in my case) or even 50 GB (see this thread (internal)).

Impacted categories

The following categories relate to this issue:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Proposal

Only back up what is necessary.

Implementation plan

Remove the line containing mv container-registry .backups from support/makefiles/Makefile.registry.mk. Then set up the registry according to https://gitlab-org.gitlab.io/gitlab-development-kit/howto/registry/.