Skip to content

How to keep working while GitLab is down

When gitlab.developers.cam.ac.uk is unavailable, you can't pull images from the GitLab container registry (registry.gitlab.developers.cam.ac.uk), install packages from GitLab package registries or run CI pipelines. This guide covers what you can still do from your own machine.

This guidebook is hosted on GitLab Pages

This guidebook is served by GitLab, so it is also unavailable when GitLab is down. Read this page before you need it.

Use what's already on your machine with logan

If .logan.yaml sets image:, logan pulls that image before every run. If GitLab is down, the pull fails. Pass --nopull to use the copy already on your machine. If the project builds from a Dockerfile, pass --nobuild instead:

logan --nopull terraform plan

With --nobuild, logan uses the image you built last time. A rebuild fails while GitLab is down if the Dockerfile's FROM line points at the GitLab registry.

Check that you have a local copy first:

docker image ls registry.gitlab.developers.cam.ac.uk/uis/devops/infra/dockerimages/logan-terraform

The local copy may be a few days old. That's fine for running Terraform, but note the version if you're debugging something that depends on it.

Terraform modules come from GitLab

terraform init can't download modules hosted on GitLab while it is down. This works only if you have already run init in this project and workspace. Don't pass --rm-terraform-data-volume or run terraform init -upgrade until GitLab is back.

Switch to the Docker Hub copies of our images

The images built by infra/dockerimages are published to the GitLab registry and to the public uisautomation organisation on Docker Hub. The names and tags match:

GitLab registry Docker Hub
registry.gitlab.developers.cam.ac.uk/uis/devops/infra/dockerimages/logan-terraform:1.17 uisautomation/logan-terraform:1.17
registry.gitlab.developers.cam.ac.uk/uis/devops/infra/dockerimages/python:3.14-alpine uisautomation/python:3.14-alpine

This only covers dockerimages, which is being deprecated. Its replacement, platform/base-images, isn't published outside GitLab yet, so this workaround won't help projects that have moved to it. We'll update this page once we've decided where base images are mirrored.

With logan

If you don't have a local copy of the logan image, override it with --image-name:

logan --image-name uisautomation/logan-terraform:1.17 terraform plan

Use the same tag as the image in the project's .logan.yaml.

In Dockerfiles and Compose files

Change FROM lines or image: keys from the GitLab registry to the Docker Hub name, for example:

FROM uisautomation/python:3.14-alpine

This is a local workaround. Don't commit it: Renovate and our pipelines expect the GitLab registry names.

Docker Hub rate limits

Docker Hub limits anonymous pulls. If you hit the limit, run docker login with your Docker account. If you have a Docker Desktop licence, use that account.

What doesn't work

  • CI pipelines and deployments that run in GitLab CI. Wait for GitLab to come back, or run the deployment locally with logan if the product supports it.
  • Images that only exist in GitLab registries, including platform/base-images and each product's own registry. Only the infra/dockerimages images are on Docker Hub, so use a local copy if you have one.
  • Installing or upgrading packages from GitLab package registries, including logan itself.
  • git pull and git push. Keep committing locally and push when GitLab is back.

Find out what's happening

The Platforms Team runs GitLab. Check the Platforms Team MS Teams channel for updates, and report the outage there if nobody else has.