From time to time, building the releases of kwctl fails. The failure happens because there's an error downloading the musl release we use to perform the cross build.
This is really bad, because it doesn't allow us to release new features/fixes.
Expected Behavior
First of all, the build should be stable. It should be green every time.
While addressing this issue, it would be nice (but not mandatory) to address also these current limitations:
We are downloading a musl release that is not versioned. This makes things not reproducible and less predictable.
When doing a SBOM, this would be problematic
Currently we are using a two stage build process. The 1st stage builds a statically linked binary for policy-server, which is then copied into a distroless container.
Maybe we can perform stage 1 inside some linux distribution container image which comes with the musl toolkit.
raulcabello
commented
2 years ago
Is there an existing issue for this?
Current Behavior
From time to time, building the releases of kwctl fails. The failure happens because there's an error downloading the musl release we use to perform the cross build.
This is really bad, because it doesn't allow us to release new features/fixes.
Expected Behavior
First of all, the build should be stable. It should be green every time.
While addressing this issue, it would be nice (but not mandatory) to address also these current limitations:
Currently we are using a two stage build process. The 1st stage builds a statically linked binary for policy-server, which is then copied into a distroless container.
Maybe we can perform stage 1 inside some linux distribution container image which comes with the musl toolkit.
Steps To Reproduce
No response
Environment
Anything else?
No response