René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"SEA building in a Linux arm64 docker container can corrupt the .gnu.hash section of the binary","articleBody":"Noticed in https://github.com/nodejs/node/pull/59582, I can only reproduce it locally using docker. The Node.js devcontainer image is enough to reproduce this when run on an arm64 host:\n\n```\ndocker pull nodejs/devcontainer:nightly\ndocker run -it nodejs/devcontainer:nightly\n```\n\nIn the container:\n\n```bash\necho 'console.log(\"hello\")' \u003e hello.js\necho '{\"main\":\"./hello.js\", \"output\":\"./sea-prep.blob\"}' \u003e sea-config.json\nnode --experimental-sea-config sea-config.json\ncp `which node` ./hello\nreadelf -x .gnu.hash ./hello | head -n 100 # shows the section filled with the symbol lookup table\nnpx postject hello NODE_SEA_BLOB sea-prep.blob --sentinel-fuse NODE_SEA_FUSE_fce680ab2cc467b6e072b8b5df1996b2\nreadelf -x .gnu.hash ./hello | head -n 100 # shows a bunch of zeros\n```\n\nThis does not reproduce on a bare-metal Linux arm64 server, or Linux x64 (bare-metal or in docker), which I think is why in the Node.js pull request it only fails in the GitHub action on Linux arm64.\n\nThe result of this is that the produced Node.js SEA cannot load any addons using `process.dlopen()`, because it cannot look up the `napi_*` symbols from itself (the same can be said about any other non-napi addons, which rely on the same mechanism to look up symbols from the binary to load the addons).","author":{"url":"https://github.com/joyeecheung","@type":"Person","name":"joyeecheung"},"datePublished":"2025-11-08T19:51:55.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/61483/node/issues/61483"}