configure -fully-static -enable-static & make
Node js compile to exe apk#
Step 2/6 : RUN apk add git python gcc g++ linux-headers make
Sending build context to Docker daemon 121.9kB configure -fully-static -enable-static & \Īnd to build: $ docker build -f Dockerfile.node -t node-static. RUN apk add git python gcc g++ linux-headers make $ docker run -ti node-static:latest /node Successfully tagged glaudiston/node-scratch:latest Removing intermediate container 2e375fc580f7 ~/src/node$ /lib64/ld-linux-x86-64.so.2 -list out/Release/nodeĪnd let's test with a docker container from scratch: ~/src/node$ cat > /tmp/Dockerfile.node-static Out/Release/node: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, BuildID=e5be29b02e283d0efdfc313e409b1a0802bd0603, with debug_info, not stripped shared-cares link to a shared cares DLL instead of static linking shared-zlib link to a shared zlib DLL instead of static linking shared-openssl link to a shared OpenSSl DLL instead of static linking shared-nghttp2 link to a shared nghttp2 DLL instead of static linking shared-libuv link to a shared libuv DLL instead of static linking Link to a shared http_parser DLL instead of static partly-static Generate an executable with libgcc and libstdc++
fully-static Generate an executable without external dynamic You can build the node statically linked yourself. I've tested the node binary in a container from scratch and it worked. As pointed by Daniel Milde, is a alternative, but its deprecated, and has no Dockerfile exposed, that do not inspire trust.
0 kommentar(er)
