[GH-ISSUE #1536] setup-node@v3 download always fails #775

Closed
opened 2026-03-01 21:46:15 +03:00 by kerem · 12 comments
Owner

Originally created by @0xBigBoss on GitHub (Dec 26, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1536

Bug report info

act version:            0.2.34
GOOS:                   darwin
GOARCH:                 amd64
NumCPU:                 16
Docker host:            DOCKER_HOST environment variable is unset/empty.
Sockets found:
        /var/run/docker.sock
        /Users/0xbigboss/.docker/run/docker.sock
Config files:           
        /Users/0xbigboss/.actrc:
                -P ubuntu-latest=catthehacker/ubuntu:act-latest
                -P ubuntu-22.04=catthehacker/ubuntu:act-22.04
                -P ubuntu-20.04=catthehacker/ubuntu:act-20.04
                -P ubuntu-18.04=catthehacker/ubuntu:act-18.04
Build info:
        Go version:            go1.19.3
        Module path:           command-line-arguments
        Main version:          
        Main path:             
        Main checksum:         
        Build settings:
                -compiler:            gc
                -ldflags:             -X main.version=0.2.34
                CGO_ENABLED:          1
                CGO_CFLAGS:           
                CGO_CPPFLAGS:         
                CGO_CXXFLAGS:         
                CGO_LDFLAGS:          
                GOARCH:               amd64
                GOOS:                 darwin
                GOAMD64:              v1
Docker Engine:
        Engine version:        22.06.0-beta.0-902-g2708be0db4.m
        Engine runtime:        runc
        Cgroup version:        2
        Cgroup driver:         cgroupfs
        Storage driver:        stargz
        Registry URI:          https://index.docker.io/v1/
        OS:                    Docker Desktop
        OS type:               linux
        OS version:            
        OS arch:               x86_64
        OS kernel:             5.15.49-linuxkit
        OS CPU:                8
        OS memory:             16010 MB
        Security options:
                name=seccomp,profile=builtin
                name=cgroupns

Command used with act

act

Describe issue

Tried to run my check command locally for the following workflow and it was not able to finish the setup-node command. Kept failing to download to the /tmp folder.

No response

Workflow content

name: Check

on: push

jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: 16.18
          cache: yarn
      - name: install
        run: |
          git config --global url."https://github.com/".insteadOf git@github.com:
          git config --global url."https://".insteadOf git://
          yarn install
      - name: lint
        run: npm run lint
      - name: test
        run: npm run test
      - name: build
        run: npm run build --config-name chrome

Relevant log output

[Check/check]   🐳  docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir=
[Check/check]   💬  ::debug::isExplicit: 
[Check/check]   💬  ::debug::explicit? false
[Check/check]   💬  ::debug::isExplicit: 12.22.12
[Check/check]   💬  ::debug::explicit? true
[Check/check]   💬  ::debug::isExplicit: 16.19.0
[Check/check]   💬  ::debug::explicit? true
[Check/check]   💬  ::debug::evaluating 0 versions
[Check/check]   💬  ::debug::match not found
| Attempting to download 16.18...
[Check/check]   💬  ::debug::No manifest cached
[Check/check]   💬  ::debug::Getting manifest from actions/node-versions@main
[Check/check]   💬  ::debug::check 18.12.1 satisfies 16.18
[Check/check]   💬  ::debug::check 18.12.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.11.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.10.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.9.1 satisfies 16.18
[Check/check]   💬  ::debug::check 18.9.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.8.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.7.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.6.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.5.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.4.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.3.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.2.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.1.0 satisfies 16.18
[Check/check]   💬  ::debug::check 18.0.0 satisfies 16.18
[Check/check]   💬  ::debug::check 16.19.0 satisfies 16.18
[Check/check]   💬  ::debug::check 16.18.1 satisfies 16.18
[Check/check]   💬  ::debug::x64===x64 && darwin===linux
[Check/check]   💬  ::debug::x64===x64 && linux===linux
[Check/check]   💬  ::debug::matched 16.18.1
| Acquiring 16.18.1 - x64 from https://github.com/actions/node-versions/releases/download/16.18.1-3486236598/node-16.18.1-linux-x64.tar.gz
[Check/check]   💬  ::debug::Downloading https://github.com/actions/node-versions/releases/download/16.18.1-3486236598/node-16.18.1-linux-x64.tar.gz
[Check/check]   💬  ::debug::Destination /tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b
[Check/check]   💬  ::debug::download failed
| ENOENT: no such file or directory, open '/tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b'
| Waiting 20 seconds before trying again
[Check/check]   💬  ::debug::download failed
| ENOENT: no such file or directory, open '/tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b'
| Waiting 11 seconds before trying again
[Check/check]   💬  ::debug::download failed
| ENOENT: no such file or directory, open '/tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b'
[Check/check]   💬  ::debug::Error: ENOENT: no such file or directory, open '/tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b'
| Falling back to download directly from Node
[Check/check]   💬  ::debug::No dist manifest cached
[Check/check]   💬  ::debug::evaluating 553 versions
[Check/check]   💬  ::debug::matched: v16.18.1
| Acquiring 16.18.1 - x64 from https://nodejs.org/dist/v16.18.1/node-v16.18.1-linux-x64.tar.gz
[Check/check]   💬  ::debug::Downloading https://nodejs.org/dist/v16.18.1/node-v16.18.1-linux-x64.tar.gz
[Check/check]   💬  ::debug::Destination /tmp/44dc3b4c-b4f0-44ed-997b-baaf9c742b31
[Check/check]   💬  ::debug::download failed
| ENOENT: no such file or directory, open '/tmp/44dc3b4c-b4f0-44ed-997b-baaf9c742b31'
| Waiting 17 seconds before trying again
[Check/check]   💬  ::debug::download failed
| ENOENT: no such file or directory, open '/tmp/44dc3b4c-b4f0-44ed-997b-baaf9c742b31'
| Waiting 16 seconds before trying again
[Check/check]   💬  ::debug::download failed
[Check/check]   ❗  ::error::ENOENT: no such file or directory, open '/tmp/44dc3b4c-b4f0-44ed-997b-baaf9c742b31'
[Check/check]   ❌  Failure - Main actions/setup-node@v3
[Check/check] exitcode '1': failure
[Check/check] 🏁  Job failed
Error: Job 'check' failed

Additional information

No response

Originally created by @0xBigBoss on GitHub (Dec 26, 2022). Original GitHub issue: https://github.com/nektos/act/issues/1536 ### Bug report info ```plain text act version: 0.2.34 GOOS: darwin GOARCH: amd64 NumCPU: 16 Docker host: DOCKER_HOST environment variable is unset/empty. Sockets found: /var/run/docker.sock /Users/0xbigboss/.docker/run/docker.sock Config files: /Users/0xbigboss/.actrc: -P ubuntu-latest=catthehacker/ubuntu:act-latest -P ubuntu-22.04=catthehacker/ubuntu:act-22.04 -P ubuntu-20.04=catthehacker/ubuntu:act-20.04 -P ubuntu-18.04=catthehacker/ubuntu:act-18.04 Build info: Go version: go1.19.3 Module path: command-line-arguments Main version: Main path: Main checksum: Build settings: -compiler: gc -ldflags: -X main.version=0.2.34 CGO_ENABLED: 1 CGO_CFLAGS: CGO_CPPFLAGS: CGO_CXXFLAGS: CGO_LDFLAGS: GOARCH: amd64 GOOS: darwin GOAMD64: v1 Docker Engine: Engine version: 22.06.0-beta.0-902-g2708be0db4.m Engine runtime: runc Cgroup version: 2 Cgroup driver: cgroupfs Storage driver: stargz Registry URI: https://index.docker.io/v1/ OS: Docker Desktop OS type: linux OS version: OS arch: x86_64 OS kernel: 5.15.49-linuxkit OS CPU: 8 OS memory: 16010 MB Security options: name=seccomp,profile=builtin name=cgroupns ``` ### Command used with act ```sh act ``` ### Describe issue Tried to run my check command locally for the following workflow and it was not able to finish the `setup-node` command. Kept failing to download to the `/tmp` folder. ### Link to GitHub repository _No response_ ### Workflow content ```yml name: Check on: push jobs: check: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - uses: actions/setup-node@v3 with: node-version: 16.18 cache: yarn - name: install run: | git config --global url."https://github.com/".insteadOf git@github.com: git config --global url."https://".insteadOf git:// yarn install - name: lint run: npm run lint - name: test run: npm run test - name: build run: npm run build --config-name chrome ``` ### Relevant log output ```sh [Check/check] 🐳 docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir= [Check/check] 💬 ::debug::isExplicit: [Check/check] 💬 ::debug::explicit? false [Check/check] 💬 ::debug::isExplicit: 12.22.12 [Check/check] 💬 ::debug::explicit? true [Check/check] 💬 ::debug::isExplicit: 16.19.0 [Check/check] 💬 ::debug::explicit? true [Check/check] 💬 ::debug::evaluating 0 versions [Check/check] 💬 ::debug::match not found | Attempting to download 16.18... [Check/check] 💬 ::debug::No manifest cached [Check/check] 💬 ::debug::Getting manifest from actions/node-versions@main [Check/check] 💬 ::debug::check 18.12.1 satisfies 16.18 [Check/check] 💬 ::debug::check 18.12.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.11.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.10.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.9.1 satisfies 16.18 [Check/check] 💬 ::debug::check 18.9.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.8.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.7.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.6.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.5.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.4.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.3.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.2.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.1.0 satisfies 16.18 [Check/check] 💬 ::debug::check 18.0.0 satisfies 16.18 [Check/check] 💬 ::debug::check 16.19.0 satisfies 16.18 [Check/check] 💬 ::debug::check 16.18.1 satisfies 16.18 [Check/check] 💬 ::debug::x64===x64 && darwin===linux [Check/check] 💬 ::debug::x64===x64 && linux===linux [Check/check] 💬 ::debug::matched 16.18.1 | Acquiring 16.18.1 - x64 from https://github.com/actions/node-versions/releases/download/16.18.1-3486236598/node-16.18.1-linux-x64.tar.gz [Check/check] 💬 ::debug::Downloading https://github.com/actions/node-versions/releases/download/16.18.1-3486236598/node-16.18.1-linux-x64.tar.gz [Check/check] 💬 ::debug::Destination /tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b [Check/check] 💬 ::debug::download failed | ENOENT: no such file or directory, open '/tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b' | Waiting 20 seconds before trying again [Check/check] 💬 ::debug::download failed | ENOENT: no such file or directory, open '/tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b' | Waiting 11 seconds before trying again [Check/check] 💬 ::debug::download failed | ENOENT: no such file or directory, open '/tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b' [Check/check] 💬 ::debug::Error: ENOENT: no such file or directory, open '/tmp/cb488b3d-bdbc-4fda-95bc-96bbc65a483b' | Falling back to download directly from Node [Check/check] 💬 ::debug::No dist manifest cached [Check/check] 💬 ::debug::evaluating 553 versions [Check/check] 💬 ::debug::matched: v16.18.1 | Acquiring 16.18.1 - x64 from https://nodejs.org/dist/v16.18.1/node-v16.18.1-linux-x64.tar.gz [Check/check] 💬 ::debug::Downloading https://nodejs.org/dist/v16.18.1/node-v16.18.1-linux-x64.tar.gz [Check/check] 💬 ::debug::Destination /tmp/44dc3b4c-b4f0-44ed-997b-baaf9c742b31 [Check/check] 💬 ::debug::download failed | ENOENT: no such file or directory, open '/tmp/44dc3b4c-b4f0-44ed-997b-baaf9c742b31' | Waiting 17 seconds before trying again [Check/check] 💬 ::debug::download failed | ENOENT: no such file or directory, open '/tmp/44dc3b4c-b4f0-44ed-997b-baaf9c742b31' | Waiting 16 seconds before trying again [Check/check] 💬 ::debug::download failed [Check/check] ❗ ::error::ENOENT: no such file or directory, open '/tmp/44dc3b4c-b4f0-44ed-997b-baaf9c742b31' [Check/check] ❌ Failure - Main actions/setup-node@v3 [Check/check] exitcode '1': failure [Check/check] 🏁 Job failed Error: Job 'check' failed ``` ### Additional information _No response_
kerem 2026-03-01 21:46:15 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 26, 2023):

Issue is stale and will be closed in 14 days unless there is new activity

<!-- gh-comment-id:1404385333 --> @github-actions[bot] commented on GitHub (Jan 26, 2023): Issue is stale and will be closed in 14 days unless there is new activity
Author
Owner

@jclusso commented on GitHub (Jan 30, 2023):

I'm seeing the same issue when installing python. Any idea what causes this. It happened after I upgraded to Docker 4.16.2. I downgraded back to 4.6.0 and it works.

<!-- gh-comment-id:1408894831 --> @jclusso commented on GitHub (Jan 30, 2023): I'm seeing the same issue when installing python. Any idea what causes this. It happened after I upgraded to Docker 4.16.2. I downgraded back to 4.6.0 and it works.
Author
Owner

@lucasmarshall commented on GitHub (Feb 1, 2023):

Also seeing this on Docker Desktop 4.16.1. Switching the file sharing implementation in the settings from VirtioFS to gRPC FUSE resolves the issue.

<!-- gh-comment-id:1411271123 --> @lucasmarshall commented on GitHub (Feb 1, 2023): Also seeing this on Docker Desktop 4.16.1. Switching the file sharing implementation in the settings from VirtioFS to gRPC FUSE resolves the issue.
Author
Owner

@Romvnly-Gaming commented on GitHub (Feb 1, 2023):

Thanks I've already committed 50 failing builds thanks to this bug. NOW I CAN FIX ON MY MACHINE WITHOUT LOOKING LIKE A IDIOT

<!-- gh-comment-id:1412122228 --> @Romvnly-Gaming commented on GitHub (Feb 1, 2023): Thanks I've already committed 50 failing builds thanks to this bug. NOW I CAN FIX ON MY MACHINE WITHOUT LOOKING LIKE A IDIOT
Author
Owner

@0xBigBoss commented on GitHub (Feb 1, 2023):

I suspect it is related to this https://github.com/docker/for-mac/issues/6243. However, I tried @lucasmarshall suggestions and it still didn't work for me. Though it's working on my Ubuntu 20.04 server just fine.

<!-- gh-comment-id:1412331048 --> @0xBigBoss commented on GitHub (Feb 1, 2023): I suspect it is related to this https://github.com/docker/for-mac/issues/6243. However, I tried @lucasmarshall suggestions and it still didn't work for me. Though it's working on my Ubuntu 20.04 server just fine.
Author
Owner

@Romvnly-Gaming commented on GitHub (Feb 6, 2023):

Reinstalled docker desktop and wsl2 and now act works fine

<!-- gh-comment-id:1419863258 --> @Romvnly-Gaming commented on GitHub (Feb 6, 2023): Reinstalled docker desktop and wsl2 and now act works fine
Author
Owner

@oynek commented on GitHub (Feb 24, 2023):

I was also on Docker 4.16.2 and setup-python@4 would not install for me either with the same error. I was already on gRPC FUSE, so it was not VirtioFS for me.

Downgrading to Docker 4.6.0 helped though.

<!-- gh-comment-id:1443843589 --> @oynek commented on GitHub (Feb 24, 2023): I was also on Docker 4.16.2 and `setup-python@4` would not install for me either with the same error. I was already on gRPC FUSE, so it was not VirtioFS for me. Downgrading to Docker `4.6.0` helped though.
Author
Owner

@alvis commented on GitHub (Mar 14, 2023):

I've tried on different combination of settings on Docker and I think I've nailed down what make the setup failed

I'm using Docker Desktop 4.17 on MacBook Pro with M1

The following settings are fine
VirtioFS
gRPC FUSE
Use Virtualization framework
Use Rosetta for x86/amd64 emulation on Apple Silicon

However, it's the containerd beta feature that makes it fail
Use containerd for pulling and storing images

@oynek @lucasmarshall You can try?

<!-- gh-comment-id:1468041001 --> @alvis commented on GitHub (Mar 14, 2023): I've tried on different combination of settings on Docker and I think I've nailed down what make the setup failed I'm using Docker Desktop 4.17 on MacBook Pro with M1 The following settings are fine ✅ VirtioFS ✅ gRPC FUSE ✅ Use Virtualization framework ✅ Use Rosetta for x86/amd64 emulation on Apple Silicon However, it's the containerd beta feature that makes it fail ❌ Use containerd for pulling and storing images @oynek @lucasmarshall You can try?
Author
Owner

@rvolz commented on GitHub (Apr 5, 2023):

FWIW, I also had this problem with Docker Desktop on Mac "::error::ENOENT: no such file or directory, open '/tmp/...". Just switching off the containerd setting, as proposed by @alvis, solved the problem.

<!-- gh-comment-id:1497532350 --> @rvolz commented on GitHub (Apr 5, 2023): FWIW, I also had this problem with Docker Desktop on Mac "::error::ENOENT: no such file or directory, open '/tmp/...". Just switching off the *containerd* setting, as proposed by @alvis, solved the problem.
Author
Owner

@jaybuidl commented on GitHub (Jun 16, 2023):

The docker image doesn't come with yarn preinstalled so it is possible that cache: yarn is causing checkout to fail.

<!-- gh-comment-id:1594491431 --> @jaybuidl commented on GitHub (Jun 16, 2023): The docker image doesn't come with yarn preinstalled so it is possible that `cache: yarn` is causing checkout to fail.
Author
Owner

@maximelebastard commented on GitHub (Sep 12, 2023):

I still have the issue on MacOS
Docker latest 24.0.5

With

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v3
        with:
          node-version: 20
          cache: "npm"
      - run: npm ci

I'm stuck on

[deploy application/build-and-deploy]   💬  ::debug::matched: v20.6.1
| Acquiring 20.6.1 - arm64 from https://nodejs.org/dist/v20.6.1/node-v20.6.1-linux-arm64.tar.gz
[deploy application/build-and-deploy]   💬  ::debug::Downloading https://nodejs.org/dist/v20.6.1/node-v20.6.1-linux-arm64.tar.gz
[deploy application/build-and-deploy]   💬  ::debug::Destination /tmp/9ac6d102-217a-4cb6-930e-7dda0dd51323
[deploy application/build-and-deploy]   💬  ::debug::download failed
| aborted
| Waiting 16 seconds before trying again

This makes act totally unusable for me as I use node in every workflow.

I suspect github actions to use cache under the hood because a local curl to https://nodejs.org/dist/v20.6.1/node-v20.6.1-linux-arm64.tar.gz gets a timeout as well.

<!-- gh-comment-id:1715378840 --> @maximelebastard commented on GitHub (Sep 12, 2023): I still have the issue on MacOS Docker latest 24.0.5 With ``` jobs: build-and-deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v3 with: node-version: 20 cache: "npm" - run: npm ci ``` I'm stuck on ``` [deploy application/build-and-deploy] 💬 ::debug::matched: v20.6.1 | Acquiring 20.6.1 - arm64 from https://nodejs.org/dist/v20.6.1/node-v20.6.1-linux-arm64.tar.gz [deploy application/build-and-deploy] 💬 ::debug::Downloading https://nodejs.org/dist/v20.6.1/node-v20.6.1-linux-arm64.tar.gz [deploy application/build-and-deploy] 💬 ::debug::Destination /tmp/9ac6d102-217a-4cb6-930e-7dda0dd51323 [deploy application/build-and-deploy] 💬 ::debug::download failed | aborted | Waiting 16 seconds before trying again ``` This makes act totally unusable for me as I use node in every workflow. I suspect github actions to use cache under the hood because a local curl to `https://nodejs.org/dist/v20.6.1/node-v20.6.1-linux-arm64.tar.gz` gets a timeout as well.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 11, 2024):

Issue is stale and will be closed in 14 days unless there is new activity

<!-- gh-comment-id:1987424815 --> @github-actions[bot] commented on GitHub (Mar 11, 2024): Issue is stale and will be closed in 14 days unless there is new activity
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#775
No description provided.