Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[@aws-cdk/aws-lambda-nodejs] Parcel v2 but Docker still needed
See original GitHub issueThe Question
According to docs https://docs.aws.amazon.com/cdk/api/latest/docs/aws-lambda-nodejs-readme.html if using Parcel v2, docker will not be necessary during build.
After adding parcel v2 and running the build in codepipeline, i still get the message that docker is required. In fact cause of lack of permission, i am getting Cannot connect to the Docker daemon at unix:///var/run/docker.sock
But why is docker needed with Parcel v2? Or did i read the docs wrong?
Environment
- CDK CLI Version: 1.61.0
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:22 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ve been watching for this issue because I’ve also been having trouble with the “local parcel” feature under Windows 10.
On my Mac, Docker-based builds work reliably but they’re very slow. Installing Parcel as per the instructions enabled faster “local parcel” as expected.
On my work Windows 10 PC, Docker-based builds have been intermittently failing with various different errors since CDK 1.58 and I’ve been hoping to use the “local parcel” to avoid those issues. However, even with CDK 1.64 and having parcel 2.0.0-beta.1 installed locally, it still tries to build with Docker.
Both computers have Node 12.8.4 and Docker 19.03.12.
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.