René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"\"undefined symbol: gcry_control\" after building in linux/amd64 alpine","articleBody":"## System information\r\n\r\n  - node version: 18.15.0\r\n  - npm or yarn version: yarn 1.22.19\r\n  - OS/version/architecture: Linux a2a48d191f5f 5.15.49-linuxkit #1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022 x86_64 GNU/Linux\r\n  - Applicable nodegit version: 0.27.0\r\n\r\n## The issue\r\n\r\nI built with following command:\r\n\r\n```sh\r\napt-get install -y libgit2-27 libgit2-dev libkrb5-dev build-essential python2\r\nalias python=python2\r\nyarn --frozen-lockfile\r\n```\r\n\r\nit builds fine, but when I try to run my project, as soon as it requires nodegit:\r\n\r\n```\r\nnode: symbol lookup error: /usr/share/apps/node_modules/nodegit/build/Release/nodegit.node: undefined symbol: gcry_control\r\n```\r\n\r\nOn my runtime I have following packages installed:\r\n\r\n```\r\napt-get install -y git libgit2-27 libkrb5-dev libssl1.1 libgcrypt20\r\n```\r\n\r\nWhen I inspect the built file with `ldd node_modules/nodegit/build/Release/nodegit.node` it says this:\r\n\r\n```\r\n\tlibgssapi_krb5.so.2 =\u003e /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x0000004001cfc000)\r\n\tlibkrb5.so.3 =\u003e /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x0000004001d4b000)\r\n\tlibk5crypto.so.3 =\u003e /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x0000004001e2b000)\r\n\tlibcom_err.so.2 =\u003e /lib/x86_64-linux-gnu/libcom_err.so.2 (0x0000004001e5f000)\r\n\tlibstdc++.so.6 =\u003e /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x0000004001e65000)\r\n\tlibm.so.6 =\u003e /lib/x86_64-linux-gnu/libm.so.6 (0x0000004001fe9000)\r\n\tlibgcc_s.so.1 =\u003e /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x000000400216c000)\r\n\tlibpthread.so.0 =\u003e /lib/x86_64-linux-gnu/libpthread.so.0 (0x0000004002188000)\r\n\tlibc.so.6 =\u003e /lib/x86_64-linux-gnu/libc.so.6 (0x00000040021a9000)\r\n\tlibkrb5support.so.0 =\u003e /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x0000004002369000)\r\n\tlibdl.so.2 =\u003e /lib/x86_64-linux-gnu/libdl.so.2 (0x0000004002378000)\r\n\tlibkeyutils.so.1 =\u003e /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x000000400237d000)\r\n\tlibresolv.so.2 =\u003e /lib/x86_64-linux-gnu/libresolv.so.2 (0x0000004002384000)\r\n\t/lib64/ld-linux-x86-64.so.2 (0x0000004000000000)\r\n```\r\n\r\n## The workaround\r\n\r\nI fixed it by running my process with `LD_PRELOAD=\"/lib/x86_64-linux-gnu/libgcrypt.so.20\" node build/server.js`\r\n\r\n## The root-cause and additional questions\r\n\r\n- Shouldn't the lib be included right at build time? It's very bad to discover a crash at runtime and not at build time 😓 \r\n- Is it possible I'll have other similar surprises at runtime, or the fact that it properly imports nodegit is enough to be reassured about this?","author":{"url":"https://github.com/nicolaschambrier","@type":"Person","name":"nicolaschambrier"},"datePublished":"2023-03-20T18:38:01.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1975/nodegit/issues/1975"}