Estimate our needs for a container registry
While experimenting with GitLab CI (#17740) we noticed the following issues when using a container registry:
- The default Docker registry (docker.io) has a limit of 100 pulls in 6h for anonymous users and 200 pulls in 6h for authenticated users (doc. We've been reaching the anonymous limit and this has been causing (Docker) jobs to fail.
- Many of our current CI jobs install dependencies inside a Docker image during the job, which might be too slow and non-deterministic (tails#18169).
- We've filled the VM disk once already with container images and had to increase disk space to avoid jobs from failing (#17824 (closed)).
- ... more? (please list here!)
If at some point we decide to use GitLab's container registry, we need to estimate mid-term disk space needs (tails#18169 (comment 165346)). Another option is to use our own container registry, and this option would also benefit from such estimation.