feat: Improve F5 WAF multi-container Docker deployment #1594
Conversation
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
This commit updates the instructions for an F5 WAF for NGINX multi-container Docker improvement to ensure that the mounts are consistent across containers and that an address is given a formal placeholder, indicating it must be replaced. This closes #1488, which also had all of the detail necessary for the fix thanks to @mrajagopal's level of detail in the issue. There is extra detail in the issue that could be used for further improvement of this use case in the future.
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
JTorreG
approved these changes
Dec 17, 2025
aknot242
reviewed
Dec 17, 2025
ADubhlaoich
commented
Dec 18, 2025
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.
Proposed changes
This commit updates the instructions for an F5 WAF for NGINX multi-container Docker improvement to ensure that the mounts are consistent across containers and that an address is given a formal placeholder, indicating it must be replaced.
This closes #1488, which also had all of the detail necessary for the fix thanks to @mrajagopal's level of detail in the issue. There is extra detail in the issue that could be used for further improvement of this use case in the future.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩