coreruleset / coreruleset/modsecurity-crs-docker
Not running with readOnlyRootFilesystem set to true
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Dockerfile
- Stars
- 448
- Forks
- 88
- Avg merge
- 6m
- Merged PRs (30d)
- 2
Description
I'm trying to run this image in my helm chart running in OCP4 whereby we have a quality gate that only allows pods with readOnlyRootFilesystem set to true. Is there perhaps hints on how to accomplish this using this image in my deployment.yaml?
Contributor guide
No contributing guide indexed for this repository
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 with the Helm deployment.yaml and the image configuration relevant to readOnlyRootFilesystem under OCP4. Reproduce the deployment with that setting enabled, then determine what prevents the image from running; done means the image starts successfully while the quality gate remains satisfied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100