-
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
[aws-lambda-python] Automatic bundling failing for PythonFunction #13245
Comments
I solved the issue by removing and purging docker from my Snap Docker install and installed Docker from the repository using the instructions from the official Docker website: https://docs.docker.com/engine/install/ubuntu/ I'm not sure what the root cause is - there certainly is something different with the Docker version in Snap. |
I had this problem too. It boils down to the fact that Docker from Snap has a different /tmp than the CDK app, so the files staged by CDK in /tmp are not accessible. |
Hmm that's unfortunate, have you found this to be the case as well @lsli8888? |
Ping me if you have additional concerns with this issue and i'll try to work through it, I'll be closing this issue now. |
|
@peterwoodworth Sorry for the late reply. Sorry, I'm not familiar or knowledgeable enough with Snap to know where it even has a temp directory. The error I saw didn't give have enough logs to help me diagnose the issue that @misterjoshua might have. But it would definitely be nice if this issue could be fixed though! |
If anyone has more information about this or wants to see it fixed, feel free to open a bug report and reference this issue. |
|
The Question
PythonFunction won't bundle files when executing cdk synth.
I created a simple project to demonstrate this and have attached. It's basically a project created cdk init in python with an invocation of PythonFunction in the stack.py file.
test-aws-lambda-python-2.zip
The error I get when executing "cdk synth" is not very descriptive. Executing cdk synth with the "--verbose" and "--trace" options don't reveal much either. I can surmise something is going wrong with building the Docker image, but I can't determine the exact Docker build command used and it doesn't return a detailed stack trace as to why the Docker build failed.
Environment
Other information
Related issue: possibly #9349
The text was updated successfully, but these errors were encountered: