Repository navigation
Containerfile.art: Add GOEXPERIMENT=strictfipsruntime for FIPS compliance - #190
Merged
bcaton85 merged 1 commit intoOct 12, 2026
Merged
Conversation
…ance Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Oct 12, 2026
bcaton85
approved these changes
Oct 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add FIPS-compliant build flags to the Go build command in
Containerfile.art.Problem
The
fbc-quay-5-0-container-security-operatorFBC is failing thefbc-fips-check-oci-taconforma check because the Go binary in the CSO image is not built with FIPS-compliant flags.Fix
Change the Go build command from:
to:
This ensures the binary passes the Enterprise Contract FIPS compliance check.
Context
Same fix as #180 (merged on
redhat-3.18).AI-generated. Review for accuracy.
@shruti-rh requested from Slack