You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project's release binaries currently require linking to glibc, which implicitly restricts which distributions of Linux SPIRE can run on. The release container images now statically link to musl to support minimal images built from scratch. We should be able to do the same for the release binaries, and ideally could just use the same binaries generated in the containers in the release pipeline.
The text was updated successfully, but these errors were encountered:
Should we create and release these musl-linked artifacts in addition to the glibc artifacts, or would it be more beneficial to solely focus on releasing musl-linked artifacts?
The project's release binaries currently require linking to glibc, which implicitly restricts which distributions of Linux SPIRE can run on. The release container images now statically link to musl to support minimal images built from scratch. We should be able to do the same for the release binaries, and ideally could just use the same binaries generated in the containers in the release pipeline.
The text was updated successfully, but these errors were encountered: