Build for AWS Lambda

[schaq8]

I'm a Linux & node noob. I'm trying to run FabricJS (which requires node-canvas) in AWS Lambda. I've been able to follow the instructions to get up and running on an AWS Linux EC2, however, Lambda has me at my wits end. Anyone have any tips or pointers on how to get this compiled for AW Lambda?

[zbjornson]

This is actually a use case for me as well. I hope to try this this weekend and will let you know what I find. I think you'll have to bundle the SOs and change bindings.gyp to point to them.

[schaq8]

Zach, I'd be so grateful!

On Thu, Nov 26, 2015 at 12:20 AM, Zach Bjornson notifications@github.com
wrote:

This is actually a use case for me as well. I hope to try this this
weekend and will let you know what I find. I think you'll have to bundle
the SOs and change bindings.gyp to point to them.

—
Reply to this email directly or view it on GitHub
#680 (comment)
.

[zbjornson]

Didn't find time this weekend, and not sure when I'll get to this. If you want to try this on your own, you might check out the commits relating to the third bullet point here: #571

[zomgbre]

+1 I'm also interested in this.

[zbjornson]

Also related: #641 (although they're not statically linking). You might find some good stuff in the forks from the people commenting there and in 571.

[ssomai]

+1 I'm also interested in this.

[mankins]

I was able to compile node-canvas and get it running on lambda by building dynamic and using rpath. Since lambda always runs in the same /var/task this makes it:

 export LDFLAGS=-Wl,-rpath=/var/task/

and then build normally.

You should also make sure you're compiling on the same AMI environment that lambda currently uses: http://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html

[jalieven]

@mankins could you provide some more info on how you dynamically build node-canvas?

[mankins]

Hey @jalieven here's some notes I made:

1. Make sure you're compiling this on the same AMI that lambda currently uses:
   http://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html
2. Lambda runs at /var/task (that's the path when you unzip), so something.so at the root of the zip file will be at /var/task/something.so.

We then want to build our libraries using an "rpath":

 export LDFLAGS=-Wl,-rpath=/var/task/

1. Compile libraries according to: https://github.com/Automattic/node-canvas/wiki/Installation---Amazon-Linux-AMI-%28EC2%29

You may want to set the prefix= ~/canvas to have all the files in one place.

1. Install node-canvas with npm
2. cd node_modules/canvas; node-gyp rebuild
3. mkdir /pkg and cp the .so files (/canvas/lib/*.so) there, using -L to dereference symlinks.
4. scp the pkg directory to the local lambda folder, possibly putting the files in the right places. (.so in root, node_modules/canvas with other libs). You'll probably want to rearrange this.

Good luck!

[jalieven]

@mankins many thanks for your notes. Works like a charm!

[mauricio-trigueros]

@mankins Can you provide more details about the process?
I tried to follow your steps, but I think I miss something, because I am not able to make it work.
I got this error in AWS lambda:

{
"errorMessage": "libpng16.so.16: cannot open shared object file: No such file or directory",
"errorType": "Error",
"stackTrace": [
"Module.load (module.js:356:32)",
"Function.Module._load (module.js:312:12)",
"Module.require (module.js:364:17)",
"require (module.js:380:17)",
"Object. (/var/task/node_modules/canvas/lib/bindings.js:2:18)",
"Module._compile (module.js:456:26)",
"Object.Module._extensions..js (module.js:474:10)",
"Module.load (module.js:356:32)",
"Function.Module._load (module.js:312:12)",
"Module.require (module.js:364:17)"
]
}

My file structure (the zip that I upload to AWS Lambda) has the next structure:

• Canvas.js
• node_modules folder
• pkg folder (with the *.so items, including libpng16.so.16)

In the AWS AMI instance that I am using to generate the zip file (same than you provide in your link), if I go to canvasexample/node_modules/canvas, and execute

ldd build/Release/canvas.node

The result that I get is:

linux-vdso.so.1 => (0x00007fff50dec000)
libpixman-1.so.0 => /usr/local/lib/libpixman-1.so.0 (0x00007fc31c71e000)
libcairo.so.2 => /usr/local/lib/libcairo.so.2 (0x00007fc31c418000)
libpng16.so.16 => /usr/local/lib/libpng16.so.16 (0x00007fc31c1e8000)
libjpeg.so.8 => /usr/local/lib/libjpeg.so.8 (0x00007fc31bfae000)
libgif.so.4 => /usr/lib64/libgif.so.4 (0x00007fc31bd9d000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fc31ba98000)
libm.so.6 => /lib64/libm.so.6 (0x00007fc31b796000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fc31b57f000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fc31b363000)
libc.so.6 => /lib64/libc.so.6 (0x00007fc31afa1000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc31cbe0000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fc31ad6b000)
libfreetype.so.6 => /usr/local/lib/libfreetype.so.6 (0x00007fc31aade000)
libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007fc31a8dc000)
libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007fc31a6d2000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fc31a4b5000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fc31a2ac000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fc319f70000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fc319d5e000)
libz.so.1 => /lib64/libz.so.1 (0x00007fc319b48000)
librt.so.1 => /lib64/librt.so.1 (0x00007fc31993f000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007fc319738000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007fc31951c000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fc3192f2000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fc3190ef000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fc318eea000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fc318ce6000)

That I guess is not correct, because (If I understand), libpng16.so.16 and the other dependencies should point to my pkg folder (may be something like "/var/task/pkg/libpng16.so.16") , that is the same I will upload to Lambda, and same that would be executed, right? (I also tried to follow another similar issue in Package pre-compiled binaries with node-canvas for downstream consumers #641.

Any help is very very welcome!

Thank you very much!

[mankins]

It sounds like you need to use the -rpath=/var/task/ of -rpath=/var/task/pkg ... you're basically baking in a search path for dynamic libs (.so) and so if you put them in pkg, you'll need to compile them that way.

[mauricio-trigueros]

Thanks! I arranged to make it work in the way you were describing.

I will continue playing with this "rpath" option!

Thanks again!

[willbamford]

I followed the process outlined by @mankins and created a GitHub repo with the compiled shared object (see src/*.so.*) files and an example with this working. Hope someone else finds this useful.

[navihtot]

Following @webseed notes I managed to get camanJS library working on AWS Lambda so here it it helps somebody.