feat(squid): run container as non-root proxy user #404
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.
Squid container previously started as root to fix mounted volume permissions, increasing impact of potential container escapes or Squid vulnerabilities.
Changes
Container security
USER proxydirective to run as non-root (UID 13, GID 13) from container startchown/chmodfrom entrypoint - no longer requires root at any point/runwritable by proxy user in Dockerfile (required for PID file)Host directory permissions
0o700→0o777(directories),0o600→0o666(files)0o777- no changes neededImplementation approach
This eliminates root access entirely from the Squid container runtime, reducing attack surface compared to privilege-dropping patterns.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.