Add ability to disable FIPS in the container, when running on FIPS enabled host
Open
Nobody has claimed this yet.
kind/feature
status/0-triage
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
It is sometimes desirable to have a container running with FIPS disabled when running on a FIPS enabled host. Would it be possible to add --fips-disable switch to the command line, which would remove the mapping to the FIPS files on the host.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Docker CLI command-line option handling and the existing path that maps FIPS files from the host into a container. Check how related flags are tested. Done means a --fips-disable option prevents that host FIPS-file mapping while preserving the current behavior when the option is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100