{{ message }}
Repository navigation
Failing to execute correct node file #538
Description
Description:
When this action is run on actions/setup-node@v3.4.0 it fails to execute node with:
/usr/local/bin/docker exec 825742ed8cb56497af43a3e9cad45d62a8173d83a0d7ee04089e4661011a3157 sh -c "cat /etc/*release | grep ^ID"
Attempting to download [14](https://github.com/Soluto-Private/trailhead/runs/7286847871?check_suite_focus=true#step:4:15)...
Acquiring 14.20.0 - x64 from https://github.com/actions/node-versions/releases/download/14.20.0-2633808318/node-14.20.0-linux-x64.tar.gz
Extracting ...
/bin/tar xz --strip 1 -C /__w/_temp/522c4b56-fe91-4c39-9441-4326bea08743 -f /__w/_temp/21d5041b-557e-46ea-9bd6-d39a79fcc807
Adding to the cache ...
Done
/__t/node/14.[20](https://github.com/Soluto-Private/trailhead/runs/7286847871?check_suite_focus=true#step:4:21).0/x64/bin/node --version
Error: There was an error when attempting to execute the process '/__t/node/14.20.0/x64/bin/node'. This may indicate the process failed to start. Error: spawn /__t/node/14.20.0/x64/bin/node ENOENT
Action version:
actions/setup-node@v3.4.0
Platform:
- Ubuntu
- macOS
- Windows
Runner type:
- Hosted
- Self-hosted
Tools version:
yarn v1.22.19
node 14.20.0
Repro steps:
Adding an action with:
- name: Use Node.js 14.x
uses: actions/setup-node@v3
with:
node-version: 14
Will trigger the issue.
Expected behavior:
I expect the install to succeed without any errors.
Actual behavior:
The installation fails when it tries to execute the node executable, specifically running the command:
node --version
Edit:
It also looks like this is only occurring with the docker container:
image: node:14-alpine
Activity
funkswing commentedon Jul 11, 2022
I had this issue as well (
image: node:16.14.2-alpine3.15)Setting
uses: actions/setup-node@v3.3.0fixed it. This is obviously a temporary fix until the issue is resolved.vsafonkin commentedon Jul 12, 2022
Hi @Gabe-Ambrosio, we will take a look at this, thanks for your report.
dmitry-shibanov commentedon Jul 12, 2022
Hello everyone. The issue comes from these lines. Internally it uses spawn method to execute it. But toolcache node versions are not compatible with alpine that is why the command getting error on the process level and it produces the issue. We prepared a pull request to fix it #540. But as temporary workaround for alpine images you can remove node-version input, because it does not affect installed node version.
Gabe-Ambrosio commentedon Jul 12, 2022
Hi @vsafonkin , I just wanted to say thank you for the prompt response and for your team's help in fixing the issue!
dmitry-shibanov commentedon Jul 13, 2022
Hello @Gabe-Ambrosio. The fix was merged to the main branch. Could you please confirm that it works as expected ?
Gabe-Ambrosio commentedon Jul 13, 2022
Hi @dmitry-shibanov , yep it looks like that fixed it! And just to be sure, I pinned the latest commit SHA when I used the action like this:
And it successfully setup node without a problem with this output:
dmitry-shibanov commentedon Jul 13, 2022
Hello @Gabe-Ambrosio. Thank you for response. I'll prefer to keep the issue open until new release.
dgaubert commentedon Jul 14, 2022
@dmitry-shibanov, do you have an ETA for the release?
Thanks in advance for maintaining it.
dmitry-shibanov commentedon Jul 15, 2022
Hello everyone. We released a new version and updated the major tag with fix. Could you please confirm that everything works as expected ?
dgaubert commentedon Jul 15, 2022
I can confirm the new release fixed the issue. Many thanks for the quick hot-fix!
Aleksanderdir commentedon Jul 15, 2022
dmitry-shibanov commentedon Jul 15, 2022
Hello @dgaubert. Thank you for your response.
For now I'm going to close the issue. If you have any concerns feel free to ping us.
chore(deps-dev): bump typescript from 5.1.6 to 5.2.2 (actions#538)