Skip to content

Run pipeline on self-managed instance to create release fails

Somehow the pipeline I try to run from the last tag (0.25.0) is failing.

First because of this error:

Error: [linux/arm64]: building at STEP "RUN apk add --no-cache curl gcompat git glab idn2-utils jq openssh-client cosign": exit status 1

I try to mitigate this by configuring the PLATFORMS variable as: linux/amd64 (instead of linux/amd64,linux/arm64). With this, the build stage seems to be completed successfully.

But now the test-integration stage fails:

image

The failed items are no links, I cannot find any logging of what is going wrong.

We are running the Gitlab runners in Kubernetes rolled out with Helm, with privileged = true.

What are the requirements of running the Gitlab CI pipeline, so I can get the (mirrored) component published in our catalog to use?

Edited by Anne Datema