Feat/owasp docker hardening rule #4 #6300 #6338
Open
Conversation
This file contains 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
[Nginx] move conf.d include to end of nginx.conf
…ges (mailcow#6273) * clamd: update to 1.4.2 + build from source instead using alpine packages * clamd: remove exposed ports from buildfile * clamd: cleanup dockerfile
Update 2025-01a
Update 2025-02
Update 2025-02
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Contribution Guidelines
What does this PR include?
Security-Feature-Request: OWASP docker hardening rule #4 #6300
Short Description
Implement OWASP docker rule #4 in the docker-compose.yml
Each single container should have:
implemented.
Affected Containers
ALL
Did you run tests?
Yes, this runs since 6 months in my setup (until now via docker-override.yml)
What were the final results? (Awaited, got)
All features and containers run stable.