GitLab CI image pinning and include ref drift across runners

GitLab CI job image drift symptom: tag pinning vs digest pinning across runners

0 reputation · 07 Nov 2022, 20:38 UTC

39.6K views0

Reproducibility gap across GitLab CI/CD runners

A team using GitLab CI/CD wants identical job execution environments across multiple runner hosts so that the same commit produces the same artifacts regardless of which runner picks up the job.

The .gitlab-ci.yml image keyword accepts registry tags or Docker-style digests, and include: project can reference another repository by branch, tag, or commit SHA. Registry tags are generally mutable, runner pull_policy and local image caches can serve previously pulled contents, and branch-based include refs advance over time. Digest and SHA pinning improve stability but add update friction and may vary in support across runner versions and executors.

Which pinning strategy for job images and included templates reliably eliminates cross-runner drift without assuming registry immutability?

How does runner pull_policy interact with cached or mirrored images to mask upstream tag changes for a specific executor?

What verification steps confirm that two runners are executing against the same image contents when the pipeline definition is identical?

Keep exploring this topic

GitLab Runner and Rails API: Job Priority Logic During Concurrent Polling

An exploration of the job priority queuing logic when multiple GitLab Runners with overlapping tags concurrently poll the Rails API for pending work.

GitLab CI/CD masked variable coverage for Base64-encoded job output

GitLab CI/CD masked variables use exact string replacement in job logs. When a secret is transformed into Base64 during execution, the encoded output may appear unmasked. Is there a configuration to mask derived representations, or is exact-match replacement the only supported behavior?

Docker : exec /usr/bin/sh: exec format error

I created a custom docker image and push it to docker hub but when I run it in CI/CD it gives me this error. exec /usr/bin/sh: exec format error Where : Dockerfile FROM ubuntu:20.04 RUN apt-get update RUN apt-get install -y software-properties-common RUN apt-get install -y python3-pip RUN pip3 install robotframework .gitlab-ci.yml robot-f

Cannot connect to the Docker daemon at tcp://localhost:2375/. Is the docker daemon running. On GitLab

I'm trying to build the CI pipeline in GitLab. I'd like to ask about making the docker work in GitLab CI. From this issue: https://gitlab.com/gitlab-org/gitlab-runner/issues/4501#note_195033385 I'm follow the instruction for both ways. With TLS and not used TLS. But It's still stuck. Which in same error Cannot connect to the Docker daemon

GitLab CI job image drift symptom: tag pinning vs digest pinning across runners

Reproducibility gap across GitLab CI/CD runners

0 answers

Your perspective belongs here.

0 question comments

Good answers start here.