-
- Downloads
feat: remove custom goreleaser image for fips and use upstream image instead
Part of https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/1312 So it turns out that we need to use CGO with Golang 1.19 in order to use the "boringcrypto" flag to build go apps in a fips compliant way. The upstream goreleaser image can't do this as it's based off alpine, so binaries come out depending on musl as their libc. However, goreleaser also provide a goreleaser image based off debian which we can use for fips builds, and will allow us to build binaries linked against regular glibc instead, allowing consumping in ubi images and other non-alpine images. This means we can drop our own goreleaser image as the upstream one (provided you use the right flags inside goreleaser) will give you what you need.
Showing
- .gitlab-ci-other-versions.yml 0 additions, 2 deletions.gitlab-ci-other-versions.yml
- .gitlab-ci.yml 0 additions, 37 deletions.gitlab-ci.yml
- Dockerfile.goreleaser-fips 0 additions, 42 deletionsDockerfile.goreleaser-fips
- goreleaser.md 3 additions, 2 deletionsgoreleaser.md
- goreleaser.yml 1 addition, 1 deletiongoreleaser.yml
- test/validate-goreleaser-fips-container-image.sh 0 additions, 7 deletionstest/validate-goreleaser-fips-container-image.sh
Dockerfile.goreleaser-fips
deleted
100644 → 0
Please register or sign in to comment