You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WOW, coming from the Ruby side where it is a simple gem install with no system dependencies needed
That’s the ideal solution, hopefully this PR will be merged #8 and all native dependencies can be removed.
Maybe at the least the README here should speak more to a docker multi-staage build/installation approach?
While multi-stage builds are possible, I find there are drawbacks too. I have to spend much more compute time building the image (especially if I’m using the ARM architecture), and frameworks like serverless still upload all stages to AWS’s ECR service, which can be upwards of 4 gigs with the multi-stage builds.
That’s an interesting approach, using GitHub Actions to publish containers you can copy from to avoid building from scratch every time. Unfortunately, there’s still the issue of #44 (comment), which means that the nodejs runtime interface client differs depending on whether you use docker containers or not (and prevents using ES Modules in the docker version).
Activity
metaskills commentedon Aug 14, 2022
WOW, coming from the Ruby side where it is a simple gem install with no system dependencies needed, this feels like something worth doing.
Maybe at the least the README here should speak more to a docker multi-staage build/installation approach?
jlarmstrongiv commentedon Aug 14, 2022
That’s the ideal solution, hopefully this PR will be merged #8 and all native dependencies can be removed.
While multi-stage builds are possible, I find there are drawbacks too. I have to spend much more compute time building the image (especially if I’m using the ARM architecture), and frameworks like serverless still upload all stages to AWS’s ECR service, which can be upwards of 4 gigs with the multi-stage builds.
That’s an interesting approach, using GitHub Actions to publish containers you can copy from to avoid building from scratch every time. Unfortunately, there’s still the issue of #44 (comment), which means that the nodejs runtime interface client differs depending on whether you use docker containers or not (and prevents using ES Modules in the docker version).
Using the new AWS Linux 2022 is nice, but getting the right version of NodeJS installed is not straightforward nodesource/distributions#1367 (comment)
@metaskills anyway, watch out for those hidden gotcha’s. I ended up building my own system to manage NodeJS C++ addons too.
metaskills commentedon Aug 15, 2022
Yup, but given the age I might have to solution something as well.
Fun fact, I do the same here for this Rust-based Lambda Extension https://github.com/customink/crypteia#installation and I think I can do something similar for our Ubuntu images.
krk commentedon Jun 23, 2023
This is fixed in #70.