Pushing from CI to registry results in error requesting bear token

Since updating from Gitlab 13.10 to 13.11 (and now 13.12) I’ve been unable to push images to the gitlab container registry. The problem is not isolated to this project but happens to other projects using different images (though very similar pipelines).

I’m using buildah to build my images and authenticating using the built in CI tokens.

If I download the job artifacts and run this job locally with my gitlab user I’m able to build and push without issues.

echo "$CI_REGISTRY_PASSWORD" | buildah login -u "$CI_REGISTRY_USER" --password-stdin $CI_REGISTRY
Login Succeeded!
buildah bud --build-arg NPM_TOKEN="$CI_JOB_TOKEN" --build-arg SENTRY_RELEASE="$CI_COMMIT_SHORT_SHA" -t "$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_NAME" .
STEP 1: FROM docker.io/node:14
Getting image source signatures
Copying blob sha256:787f5e2f10471c11a2064774062aeeb400f76e9eef1ca768156a23678f005f3e
Copying blob sha256:bd821d20ef8c23c1c474d4b014889cfd2fcffb063a86dea8769347a630d0d558
Copying blob sha256:dc05be471d511acb4574f2f3630582527220c59d0abf0b8b905769916b550da7
Copying blob sha256:7b6173a10eb81a318ed53df74c8b80d29656f68194682e51f46f9b7b24c6ba03
Copying blob sha256:55fab5cadd3cc0fb680b701177abf2c36dde0de9f1e3f3b233aab8ba622c4d48
Copying blob sha256:bfde2ec33fbca3c74c6e91bca3fbcb22ed2972671d49a1accb7089c9473cac12
Copying blob sha256:9b7ece606ebf0a0f6488414e45f06ca2355687ab9b784d428542b843feb899f6
Copying blob sha256:85c5bb1fa3e3e86e4f9ccbf2480ac768a80bf25f48f8d2f17b6c7e119e4e7e6b
Copying blob sha256:94ab3cac57c49280dec1fbcdb22af539cb18f628b50b9b6b55a9d0b32f77c5fd
Copying config sha256:9153ee3e2ced316fb30612aa14f7b787711e94ca65afa452af9ca9b79574dce3
Writing manifest to image destination
Storing signatures
STEP 2: WORKDIR /usr/src/app
STEP 3: ARG NPM_TOKEN
STEP 4: ARG SENTRY_RELEASE
STEP 5: COPY .npmrc .npmrc
STEP 6: RUN echo //myselfhostedgitlab.com/api/v4/packages/npm/:_authToken=${NPM_TOKEN} >> .npmrc
STEP 7: COPY package*.json ./
STEP 8: RUN npm ci --production
added 782 packages in 30.153s
STEP 9: RUN rm -f .npmrc
STEP 10: COPY *.md ./
STEP 11: COPY dist dist
STEP 12: RUN echo SENTRY_RELEASE=${SENTRY_RELEASE} >> .env
STEP 13: EXPOSE 8080
STEP 14: USER node
STEP 15: CMD ["node", "dist/main.js"]
STEP 16: COMMIT docker.myselfhostedgitlab.com:443/my-project:master
Getting image source signatures
Copying blob sha256:2f4ee6a2e1b5dfb9236cd262e788f9d39109242ca27a4aacb583c8af66ec3ff7
Copying blob sha256:8c8e652ecd8f418903f7c91efb9a3f636ac6bb989d97d9a77dc0ff1ffe39e572
Copying blob sha256:ed0a3d9cbcc76c5ccd3ffe6858fcdca6f918bb9090b2bee10e2fc6aa55bef856
Copying blob sha256:cddb98d7716306089e53c966735fab14c5108e48a020261d42a839ed179a570e
Copying blob sha256:1e9c28d06610a2e382ba5827a10fe96dc7ddabcaf2919a2647216f296077ddd2
Copying blob sha256:b257e69d416ffc0ebfbec0ba9e716e37f5ca8d66986525ab42b27e9e23f64044
Copying blob sha256:b1501adb30374ad055063b09275e5cdbe59d0de5cf6836f075d535195ee60fef
Copying blob sha256:4a844761bb65d18f051801a29987be722433bf78b56460e4c22bf427a77b18ef
Copying blob sha256:b238f928d38b8c3c1221d4506f4cf58999ba164db3c68d2efc385990982f6d68
Copying blob sha256:4ac05ac93799714c302e493c066bbba1ebb229a2e52f6b233356145528dd7f28
Copying config sha256:8a235d0c89f540002c67e19e36112970f796560dcc904a9d3496b19e42f2af13
Writing manifest to image destination
Storing signatures
--> 8a235d0c89f
8a235d0c89f540002c67e19e36112970f796560dcc904a9d3496b19e42f2af13
buildah push "$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_NAME"
Getting image source signatures
error pushing image "docker.myselfhostedgitlab.com:443/my-project:master" to "docker://docker.myselfhostedgitlab.com:443/my-project:master": error copying layers and metadata from "containers-storage:[vfs@/var/lib/containers/storage+/run/containers/storage:vfs.imagestore=/var/lib/shared]docker.myselfhostedgitlab.com:443/my-project:master" to "docker://docker.myselfhostedgitlab.com:443/my-project:master": Error trying to reuse blob sha256:2f4ee6a2e1b5dfb9236cd262e788f9d39109242ca27a4aacb583c8af66ec3ff7 at destination: Requesting bear token: invalid status code from registry 403 (Forbidden)
level=error msg="exit status 125"

This exact same pipeline ran fine in gitlab 13.10

Nobody have any idea what the problem might be?