docs: incorrect port mappings (--publish 80:80) for unprivileged container images #478
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
Fix #428
- Explains that unprivileged images listen on port 8080 (not 80)
- Shows correct port mapping: --publish 80:8080
- Provides alternative mapping: --publish 8080:8080 (avoids requiring privileges on host)
- Uses example tag: unprivileged-oss-20250718
- Added clarification that unprivileged images need containerPort: 8080 instead of containerPort: 80
- Documented security benefits of unprivileged containers
- Clarified the distinction between standard OSS (port 80, runs as root) and unprivileged (port 8080, runs as nginx user) variants
Checklist
Before creating a pull request (PR), run through this checklist and mark each as complete:
README.md).