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
I am not an SME around image-building, true. I do know that there are a lot of things to be careful of, if you want FIPS-mode to work - including how things are compiled. If we're not doing them (and I suspect we're not), you'll get errors like this. It could be something as simple as "not including the expected HMACs as part of the install process", IIRC. FIPS-mode is Very Picky (as it should be) - it's generally not as simple/easy as "turn it on".
@ggainey
I greatly appreciate your response.
I'm not compiling any images. I am simply using the image versions provided from docker hub or quay.io. I had sort of presumed FIPS support would be working. I was hoping somebody who knew the codebase could confirm if any FIPS capability exists or do I need to compile a custom version to get it to work.
Version
all images pulled are from docker hub
(deploment via single container)
pulp:latest
OR
(deployment via multiple containers with compose)
pulp-minimal:latest
pulp-web:latest
redis:latest
postgres:13
Describe the bug
Images will not run with FIPS enabled
To Reproduce
Enable or disable FIPS and observe the logs
Expected behavior
The containers should start with FIPS enabled
Additional context
ENVIRONMENT:
Run the single container with FIPS on
Run the single container with FIPS off
I get valid output from curl at this point.
Run multiple containers using compose with FIPS on
Run multiple containers using compose with FIPS off
Again I get valid output from curl after waiting a few minutes for everything to be provisioned.
The text was updated successfully, but these errors were encountered: