GitLab: Container Registry

Long-Standing Issue: Unknown Error Pulling Private Images from GitLab Container Registry

In February 2020 I filed a GitLab issue that would go on to stay open for over four years, accumulate numerous comments and citations from engineers around the world, and highlight a real behavioral difference between competing container registry implementations.

Full details: gitlab.com/gitlab-org/gitlab/-/issues/205936

Many things in the software and DevOps space can become huge rabbit-holes, where sometimes the only effective solution is to use another provider’s offering short-term (often long-term), or to fall back to an older version of a tool.

This hard-to-debug issue – related to the GitLab Container Registry – is a good example of the complexity introduced when different implementations claim to provide identical features. In this case, the Quay.io offering and the GitLab offering have a notable behavioral difference, despite both presenting as standard OCI-compatible registries.

Due to my deep experience working with Docker containers and Kubernetes, I was likely the first person to encounter this issue in the field, and I am proud to have been the first to report it to the GitLab team and the wider open source community.