Anyone have experience with using jailkit to deploy a node app?

I have set up a minimal jail environment and used jk_cp to copy in the node 
binary (and auto-detected .so files):'

ubuntu@ip-10-158-7-212:~/intl$ sudo jk_cp -v /opt/jail /usr/local/bin/node
Copying /usr/local/bin/node to /opt/jail/usr/local/bin/node
/opt/jail/lib/x86_64-linux-gnu/libdl.so.2 already exists, will not touch it
/opt/jail/lib/x86_64-linux-gnu/librt.so.1 already exists, will not touch it
/opt/jail/usr/lib/x86_64-linux-gnu/libstdc++.so.6 already exists, will not 
touch it
/opt/jail/lib/x86_64-linux-gnu/libm.so.6 already exists, will not touch it
/opt/jail/lib/x86_64-linux-gnu/libgcc_s.so.1 already exists, will not touch 
it
/opt/jail/lib/x86_64-linux-gnu/libpthread.so.0 already exists, will not 
touch it
/opt/jail/lib/x86_64-linux-gnu/libc.so.6 already exists, will not touch it
/opt/jail/lib64/ld-linux-x86-64.so.2 already exists, will not touch it

and running a simple "hello world" http server works. However when I run my 
actual app, amino-deploy <https://github.com/amino/amino-deploy> , I get an 
immediate "Segmentation fault (core dumped)" and in syslog

"Mar  1 21:28:28 ip-10-158-7-212 kernel: [9162951.853559] node[19359]: 
segfault at 0 ip 00007f0d35d9a25f sp 00007fffb3875878 error 4 in 
libc-2.15.so[7f0d35c60000+1b5000]"


It seems that jk_cp might've missed some stuff to copy. Any advice on how 
to debug this?

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to