fix(tooling): container user's uid does not match host's uid #20082
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.
Docker
jsii/superchain
image, which is used as a base image of devcontainer, has adefault non-root user
superchain
which UID is1001
.If the container host's workspace directory is not owned by UID
1001
, users may not beable to modify files inside the container because of the insufficient permission.
.devcontainer.json has a workaround option
updateRemoteUserUID
which updates container's non-root user's UID at runtime.
This PR sets
remoteUser
explicitly in .devcontainer.json to makeupdateRemoteUserUID
work.fixes #19979
All Submissions:
Adding new Unconventional Dependencies:
New Features
yarn integ
to deploy the infrastructure and generate the snapshot (i.e.yarn integ
without--dry-run
)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license