[aws-lambda-python] Building fails: cp: preserving times for ‘/asset-output/.’: Operation not permitted for Python 3.8 runtime #9704
Assignees
Labels
@aws-cdk/aws-lambda-python
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
in-progress
This issue is being actively worked on.
p1
Comments
CarlosDomingues
added
bug
|
Did a quick test and I'm getting the same error for the Python 3.7 runtime. |
|
@adamelmore can you please take a look? |
SomayaB
added
in-progress
mergify bot
pushed a commit
that referenced
this issue
Aug 19, 2020
Fixes #9704. `aws-lambda-python` originally used `rsync` to move lambda code into `/asset-output`, but I switched to `cp` in #9355 to resolve #9349 as `rsync` isn't installed in the python3.8 sam docker image. This change introduces a Dockerfile derived from the `bundlingDockerImage` of the runtime which installs `rsync` if it's missing. While this feels a bit heavy-handed, I had been planning to introduce a Dockerfile to setup a working pip cache after #9582 lands. I'm also happy to take a different approach if you'd prefer, @eladb. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
misterjoshua
pushed a commit
to misterjoshua/aws-cdk
that referenced
this issue
Aug 19, 2020
Fixes aws#9704. `aws-lambda-python` originally used `rsync` to move lambda code into `/asset-output`, but I switched to `cp` in aws#9355 to resolve aws#9349 as `rsync` isn't installed in the python3.8 sam docker image. This change introduces a Dockerfile derived from the `bundlingDockerImage` of the runtime which installs `rsync` if it's missing. While this feels a bit heavy-handed, I had been planning to introduce a Dockerfile to setup a working pip cache after aws#9582 lands. I'm also happy to take a different approach if you'd prefer, @eladb. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to fix #9324 , the bundling image used by aws-lambda-python now uses
cpinstead ofrsync(which was not present in the container) to copy assets to the output folder. However, now I'm getting the following error:Reproduction Steps
Same as before.
Environment
The text was updated successfully, but these errors were encountered: