fix(dev-stack): run web containers as local user#1422
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
.dev/dev.envweb-permissionsinit service to prepare shared web volumes and.nextfor that UID/GIDRoot Cause
The Docker dev stack used the default root user from
node:24-bookworm-slim, so bind-mounted Next/Turbopack cache files underapps/web/.nextwere generated asroot:rooton developer machines.Validation
bash deploy/scripts/test-dev-stack.shdocker compose --project-name ct-ops-dev-user-test --env-file .dev/dev.env -f docker-compose.dev-stack.yml configweb-devruntime check confirmed the container ran as the generated UID/GID and could write.next,node_modules, pnpm store, and Corepack cache paths.