-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(core): asset bundling fails for non-existent user #15313
fix(core): asset bundling fails for non-existent user #15313
Conversation
7f58ce1
to
6f50ee9
Compare
Please don't forget to describe the bug you are fixing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build is failing, and needs a description appropriate for the changelog. Why would someone reading the changelog care about this change?
The user is only needed when bundling via Docker so there is no need to always call os.userInfo() as a default fallback even when bundling locally. Additionally, calling os.userInfo() can easily fail when already running inside a Docker container with non-existent uid and gid (e.g. when using the Jenkins Docker plugin).
6f50ee9
to
1c66380
Compare
@rix0rrr I've updated the PR title and description and the build was successful this time around. |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Currently, when not explicitly passing a user in BundlingOptions, `os.userInfo()` is called as a default fallback. Even though the user is only used and needed when using docker bundling, it is still called when using local bundling. This can be problematic e.g. when running cdk scripts inside a docker container where the user does not exist inside the container (see aws#15415). Fixes aws#15415. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Currently, when not explicitly passing a user in BundlingOptions, `os.userInfo()` is called as a default fallback. Even though the user is only used and needed when using docker bundling, it is still called when using local bundling. This can be problematic e.g. when running cdk scripts inside a docker container where the user does not exist inside the container (see aws#15415). Fixes aws#15415. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Currently, when not explicitly passing a user in BundlingOptions,
os.userInfo()
is called as a default fallback. Even though the user is only used and needed when using docker bundling, it is still called when using local bundling. This can be problematic e.g. when running cdk scripts inside a docker container where the user does not exist inside the container (see #15415).Fixes #15415.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license