starred/act
1
0
Fork 0
mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00
Code Issues 289 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #834] exec: "node": executable file not found in $PATH: unknown #507

New issue
Closed
opened 2026-03-01 21:44:01 +03:00 by kerem · 10 comments
kerem commented 2026-03-01 21:44:01 +03:00
Owner
Copy link

Originally created by @GabrieleCalarota on GitHub (Oct 6, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/834

System information

  • Operating System: Ubuntu 18
  • Architecture: arm64 (64-bit)
  • Apple M1: no
  • Docker version: Docker version 20.10.8, build 3967b7d28e
  • Docker image used in act:
  • act version: 0.2.19

Expected behaviour

Should run without errors

Actual behaviour

Docker fails not finding node exec in PATH

Workflow and/or repository

https://github.com/SquisEat/pull-request-comment-trigger

workflow 
name: Pull Request Comment Trigger Example
on:
  pull_request:
    types: [opened]
  issue_comment:
    types: [created]

jobs:

  eyes:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
        with:
          path: "pull-request-comment-trigger"

      - name: Setup NodeJS 14
        uses: actions/setup-node@v1
        with:
          node-version: 12

      - uses: ./
        id: check
        with:
          trigger: 'look'
          prefix_only: 'true'
          reaction: rocket
        env:
          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
      - run: 'echo Found it!'
        if: steps.check.outputs.triggered == 'true'

Steps to reproduce

act output

Log

act -v issue_comment

gabriele@gabriele-pc:~/WebstormProjects/pull-request-comment-trigger$ act -v issue_comment
DEBU[0000] Loading environment from /home/gabriele/WebstormProjects/pull-request-comment-trigger/.env 
DEBU[0000] Loading secrets from /home/gabriele/WebstormProjects/pull-request-comment-trigger/.secrets 
DEBU[0000] Loading workflows from '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.github/workflows' 
DEBU[0000] Reading workflow '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.github/workflows/example.yml' 
DEBU[0000] Planning event: issue_comment                
DEBU[0000] Loading slug from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' 
DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 
DEBU[0000] Loading revision from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' 
DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 
DEBU[0000] HEAD points to '3c47c5b187c004d1017e8d464b77e3b250d4e614' 
DEBU[0000] HEAD matches refs/heads/master               
DEBU[0000] using github ref: refs/heads/master          
DEBU[0000] context env => map[ACT:true]                 
[Pull Request Comment Trigger Example/eyes] 🚀  Start image=catthehacker/ubuntu:act-latest
DEBU[0000] Loading slug from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' 
DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 
DEBU[0000] Loading revision from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' 
DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 
DEBU[0000] HEAD points to '3c47c5b187c004d1017e8d464b77e3b250d4e614' 
DEBU[0000] HEAD matches refs/heads/master               
DEBU[0000] using github ref: refs/heads/master          
[Pull Request Comment Trigger Example/eyes]   🐳  docker pull catthehacker/ubuntu:act-latest
DEBU[0000] Image exists? true                           
[Pull Request Comment Trigger Example/eyes] Removed container: 0544478c0f2b21fe1804390be84733349a3beb4bf44089b98beb66de35be0b70
[Pull Request Comment Trigger Example/eyes]   🐳  docker volume rm act-Pull-Request-Comment-Trigger-Example-eyes
[Pull Request Comment Trigger Example/eyes]   🐳  docker create image=catthehacker/ubuntu:act-latest entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Pull Request Comment Trigger Example/eyes] Created container name=act-Pull-Request-Comment-Trigger-Example-eyes id=6e5fa6197c544ca4696d0d46efc07e6f4456030d16aa6a465c2ee5179b1ec4c8 from image catthehacker/ubuntu:act-latest
[Pull Request Comment Trigger Example/eyes] ENV ==> [RUNNER_TOOL_CACHE=/opt/hostedtoolcache RUNNER_OS=Linux RUNNER_TEMP=/tmp]
[Pull Request Comment Trigger Example/eyes]   🐳  docker run image=catthehacker/ubuntu:act-latest entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Pull Request Comment Trigger Example/eyes] Starting container: 6e5fa6197c544ca4696d0d46efc07e6f4456030d16aa6a465c2ee5179b1ec4c8
[Pull Request Comment Trigger Example/eyes] Started container: 6e5fa6197c544ca4696d0d46efc07e6f4456030d16aa6a465c2ee5179b1ec4c8
DEBU[0000] Writing entry to tarball workflow/event.json len:2 
DEBU[0000] Writing entry to tarball workflow/envs.txt len:0 
DEBU[0000] Writing entry to tarball home/.act len:0     
[Pull Request Comment Trigger Example/eyes] Extracting content to '/github/'
DEBU[0000] Loading slug from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' 
DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 
DEBU[0000] Loading revision from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' 
DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 
DEBU[0000] HEAD points to '3c47c5b187c004d1017e8d464b77e3b250d4e614' 
DEBU[0000] HEAD matches refs/heads/master               
DEBU[0000] using github ref: refs/heads/master          
DEBU[0001] Loading slug from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' 
DEBU[0001] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 
DEBU[0001] Loading revision from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' 
DEBU[0001] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 
DEBU[0001] HEAD points to '3c47c5b187c004d1017e8d464b77e3b250d4e614' 
DEBU[0001] HEAD matches refs/heads/master               
DEBU[0001] using github ref: refs/heads/master          
DEBU[0001] context env => map[ACT:true]                 
DEBU[0001] context env => map[ACT:true CI:true GITHUB_ACTION:check GITHUB_ACTIONS:true GITHUB_ACTOR:nektos/act GITHUB_ENV:/github/workflow/envs.txt GITHUB_EVENT_NAME:issue_comment GITHUB_EVENT_PATH:/github/workflow/event.json GITHUB_REF:refs/heads/master GITHUB_REPOSITORY:SquisEat/pull-request-comment-trigger GITHUB_RUN_ID:1 GITHUB_RUN_NUMBER:1 GITHUB_SHA:3c47c5b187c004d1017e8d464b77e3b250d4e614 GITHUB_TOKEN: GITHUB_WORKFLOW:Pull Request Comment Trigger Example GITHUB_WORKSPACE:/github/workspace HOME:/github/home INPUT_PREFIX_ONLY:true INPUT_REACTION:rocket INPUT_TRIGGER:look] 
DEBU[0001] setupEnv: map[ACT:true CI:true GITHUB_ACTION:check GITHUB_ACTIONS:true GITHUB_ACTOR:nektos/act GITHUB_ENV:/github/workflow/envs.txt GITHUB_EVENT_NAME:issue_comment GITHUB_EVENT_PATH:/github/workflow/event.json GITHUB_REF:refs/heads/master GITHUB_REPOSITORY:SquisEat/pull-request-comment-trigger GITHUB_RUN_ID:1 GITHUB_RUN_NUMBER:1 GITHUB_SHA:3c47c5b187c004d1017e8d464b77e3b250d4e614 GITHUB_TOKEN: GITHUB_WORKFLOW:Pull Request Comment Trigger Example GITHUB_WORKSPACE:/github/workspace HOME:/github/home INPUT_PREFIX_ONLY:true INPUT_REACTION:rocket INPUT_TRIGGER:look] 
[Pull Request Comment Trigger Example/eyes] ⭐  Run ./
DEBU[0001] Read action &{Pull Request Comment Trigger v1.0.1  Look for a "trigger word" in a pull-request description or comment, so that later steps can know whether or not to run. map[prefix_only:{If 'true', the trigger must match the start of the comment. false false} reaction:{If set, the specified emoji "reaction" is put on the comment to indicate that the trigger was detected. For example, "rocket". false } trigger:{The string to look for in pull-request descriptions and comments. For example "#build/android" true }] map[comment_body:{The comment body.} triggered:{the string 'true' if the trigger was found, otherwise the string 'false'}] {node12 map[] dist/index.js  [] []} {red check-circle}} from '/home/gabriele/WebstormProjects/pull-request-comment-trigger/action.yml' 
DEBU[0001] About to run action &{Pull Request Comment Trigger v1.0.1  Look for a "trigger word" in a pull-request description or comment, so that later steps can know whether or not to run. map[prefix_only:{If 'true', the trigger must match the start of the comment. false false} reaction:{If set, the specified emoji "reaction" is put on the comment to indicate that the trigger was detected. For example, "rocket". false } trigger:{The string to look for in pull-request descriptions and comments. For example "#build/android" true }] map[comment_body:{The comment body.} triggered:{the string 'true' if the trigger was found, otherwise the string 'false'}] {node12 map[] dist/index.js  [] []} {red check-circle}} 
DEBU[0001] type=2 actionDir=/home/gabriele/WebstormProjects/pull-request-comment-trigger actionPath= Workdir=/home/gabriele/WebstormProjects/pull-request-comment-trigger ActionCacheDir=/home/gabriele/.cache/act actionName=pull-request-comment-trigger containerActionDir=/github/workspace 
DEBU[0001] executing remote job container: [node /github/workspace/pull-request-comment-trigger/dist/index.js] 
[Pull Request Comment Trigger Example/eyes] Exec command '[node /github/workspace/pull-request-comment-trigger/dist/index.js]'
| OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "node": executable file not found in $PATH: unknown
[Pull Request Comment Trigger Example/eyes]   ❌  Failure - ./
DEBU[0001] exit with `FAILURE`: 126                     
DEBU[0001] exit with `FAILURE`: 126                     
Error: exit with `FAILURE`: 126
</details>
Originally created by @GabrieleCalarota on GitHub (Oct 6, 2021). Original GitHub issue: https://github.com/nektos/act/issues/834 <!-- - Make sure you are able to reproduce it on the [latest version](https://github.com/nektos/act/releases) - Search the existing issues. - Refer to [README](https://github.com/nektos/act/blob/master/README.md). --> ## System information <!-- - Operating System: < Windows | Linux | macOS | etc... > - Architecture: < x64 (64-bit) | x86 (32-bit) | arm64 (64-bit) | arm (32-bit) | etc... > - Apple M1: < yes | no > - Docker version: < output of `docker system info -f "{{.ServerVersion}}"` > - Docker image used in `act`: < can be omitted if it's included in log > - `act` version: < output of `act --version`, if you've built `act` yourself, please provide commit hash > --> - Operating System: Ubuntu 18 - Architecture: arm64 (64-bit) - Apple M1: no - Docker version: Docker version 20.10.8, build 3967b7d28e - Docker image used in `act`: - `act` version: 0.2.19 ## Expected behaviour Should run without errors <!-- - Describe how whole process should go and finish --> ## Actual behaviour Docker fails not finding node exec in PATH <!-- - Describe the issue --> ## Workflow and/or repository <!-- - Provide workflow with which we can reproduce the issue OR - Provide link to your GitHub repository that contains the workflow --> https://github.com/SquisEat/pull-request-comment-trigger <details> <summary>workflow</summary> ```none name: Pull Request Comment Trigger Example on: pull_request: types: [opened] issue_comment: types: [created] jobs: eyes: runs-on: ubuntu-latest steps: - name: Checkout uses: actions/checkout@v2 with: path: "pull-request-comment-trigger" - name: Setup NodeJS 14 uses: actions/setup-node@v1 with: node-version: 12 - uses: ./ id: check with: trigger: 'look' prefix_only: 'true' reaction: rocket env: GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}' - run: 'echo Found it!' if: steps.check.outputs.triggered == 'true' ``` </details> ## Steps to reproduce <!-- - Make sure to include full command with parameters you used to run `act`, example: 1. Clone example repo (https://github.com/cplee/github-actions-demo) 2. Enter cloned repo directory 3. Run `act -s SUPER_SECRET=im-a-value` --> ## `act` output <!-- - Use `act` with `-v`/`--verbose` and paste output from your terminal in code block below --> <details> <summary>Log</summary> `act -v issue_comment` ```none gabriele@gabriele-pc:~/WebstormProjects/pull-request-comment-trigger$ act -v issue_comment DEBU[0000] Loading environment from /home/gabriele/WebstormProjects/pull-request-comment-trigger/.env DEBU[0000] Loading secrets from /home/gabriele/WebstormProjects/pull-request-comment-trigger/.secrets DEBU[0000] Loading workflows from '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.github/workflows' DEBU[0000] Reading workflow '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.github/workflows/example.yml' DEBU[0000] Planning event: issue_comment DEBU[0000] Loading slug from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 DEBU[0000] Loading revision from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 DEBU[0000] HEAD points to '3c47c5b187c004d1017e8d464b77e3b250d4e614' DEBU[0000] HEAD matches refs/heads/master DEBU[0000] using github ref: refs/heads/master DEBU[0000] context env => map[ACT:true] [Pull Request Comment Trigger Example/eyes] 🚀 Start image=catthehacker/ubuntu:act-latest DEBU[0000] Loading slug from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 DEBU[0000] Loading revision from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 DEBU[0000] HEAD points to '3c47c5b187c004d1017e8d464b77e3b250d4e614' DEBU[0000] HEAD matches refs/heads/master DEBU[0000] using github ref: refs/heads/master [Pull Request Comment Trigger Example/eyes] 🐳 docker pull catthehacker/ubuntu:act-latest DEBU[0000] Image exists? true [Pull Request Comment Trigger Example/eyes] Removed container: 0544478c0f2b21fe1804390be84733349a3beb4bf44089b98beb66de35be0b70 [Pull Request Comment Trigger Example/eyes] 🐳 docker volume rm act-Pull-Request-Comment-Trigger-Example-eyes [Pull Request Comment Trigger Example/eyes] 🐳 docker create image=catthehacker/ubuntu:act-latest entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[] [Pull Request Comment Trigger Example/eyes] Created container name=act-Pull-Request-Comment-Trigger-Example-eyes id=6e5fa6197c544ca4696d0d46efc07e6f4456030d16aa6a465c2ee5179b1ec4c8 from image catthehacker/ubuntu:act-latest [Pull Request Comment Trigger Example/eyes] ENV ==> [RUNNER_TOOL_CACHE=/opt/hostedtoolcache RUNNER_OS=Linux RUNNER_TEMP=/tmp] [Pull Request Comment Trigger Example/eyes] 🐳 docker run image=catthehacker/ubuntu:act-latest entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[] [Pull Request Comment Trigger Example/eyes] Starting container: 6e5fa6197c544ca4696d0d46efc07e6f4456030d16aa6a465c2ee5179b1ec4c8 [Pull Request Comment Trigger Example/eyes] Started container: 6e5fa6197c544ca4696d0d46efc07e6f4456030d16aa6a465c2ee5179b1ec4c8 DEBU[0000] Writing entry to tarball workflow/event.json len:2 DEBU[0000] Writing entry to tarball workflow/envs.txt len:0 DEBU[0000] Writing entry to tarball home/.act len:0 [Pull Request Comment Trigger Example/eyes] Extracting content to '/github/' DEBU[0000] Loading slug from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 DEBU[0000] Loading revision from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' DEBU[0000] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 DEBU[0000] HEAD points to '3c47c5b187c004d1017e8d464b77e3b250d4e614' DEBU[0000] HEAD matches refs/heads/master DEBU[0000] using github ref: refs/heads/master DEBU[0001] Loading slug from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' DEBU[0001] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 DEBU[0001] Loading revision from git directory '/home/gabriele/WebstormProjects/pull-request-comment-trigger/.git' DEBU[0001] Found revision: 3c47c5b187c004d1017e8d464b77e3b250d4e614 DEBU[0001] HEAD points to '3c47c5b187c004d1017e8d464b77e3b250d4e614' DEBU[0001] HEAD matches refs/heads/master DEBU[0001] using github ref: refs/heads/master DEBU[0001] context env => map[ACT:true] DEBU[0001] context env => map[ACT:true CI:true GITHUB_ACTION:check GITHUB_ACTIONS:true GITHUB_ACTOR:nektos/act GITHUB_ENV:/github/workflow/envs.txt GITHUB_EVENT_NAME:issue_comment GITHUB_EVENT_PATH:/github/workflow/event.json GITHUB_REF:refs/heads/master GITHUB_REPOSITORY:SquisEat/pull-request-comment-trigger GITHUB_RUN_ID:1 GITHUB_RUN_NUMBER:1 GITHUB_SHA:3c47c5b187c004d1017e8d464b77e3b250d4e614 GITHUB_TOKEN: GITHUB_WORKFLOW:Pull Request Comment Trigger Example GITHUB_WORKSPACE:/github/workspace HOME:/github/home INPUT_PREFIX_ONLY:true INPUT_REACTION:rocket INPUT_TRIGGER:look] DEBU[0001] setupEnv: map[ACT:true CI:true GITHUB_ACTION:check GITHUB_ACTIONS:true GITHUB_ACTOR:nektos/act GITHUB_ENV:/github/workflow/envs.txt GITHUB_EVENT_NAME:issue_comment GITHUB_EVENT_PATH:/github/workflow/event.json GITHUB_REF:refs/heads/master GITHUB_REPOSITORY:SquisEat/pull-request-comment-trigger GITHUB_RUN_ID:1 GITHUB_RUN_NUMBER:1 GITHUB_SHA:3c47c5b187c004d1017e8d464b77e3b250d4e614 GITHUB_TOKEN: GITHUB_WORKFLOW:Pull Request Comment Trigger Example GITHUB_WORKSPACE:/github/workspace HOME:/github/home INPUT_PREFIX_ONLY:true INPUT_REACTION:rocket INPUT_TRIGGER:look] [Pull Request Comment Trigger Example/eyes] ⭐ Run ./ DEBU[0001] Read action &{Pull Request Comment Trigger v1.0.1 Look for a "trigger word" in a pull-request description or comment, so that later steps can know whether or not to run. map[prefix_only:{If 'true', the trigger must match the start of the comment. false false} reaction:{If set, the specified emoji "reaction" is put on the comment to indicate that the trigger was detected. For example, "rocket". false } trigger:{The string to look for in pull-request descriptions and comments. For example "#build/android" true }] map[comment_body:{The comment body.} triggered:{the string 'true' if the trigger was found, otherwise the string 'false'}] {node12 map[] dist/index.js [] []} {red check-circle}} from '/home/gabriele/WebstormProjects/pull-request-comment-trigger/action.yml' DEBU[0001] About to run action &{Pull Request Comment Trigger v1.0.1 Look for a "trigger word" in a pull-request description or comment, so that later steps can know whether or not to run. map[prefix_only:{If 'true', the trigger must match the start of the comment. false false} reaction:{If set, the specified emoji "reaction" is put on the comment to indicate that the trigger was detected. For example, "rocket". false } trigger:{The string to look for in pull-request descriptions and comments. For example "#build/android" true }] map[comment_body:{The comment body.} triggered:{the string 'true' if the trigger was found, otherwise the string 'false'}] {node12 map[] dist/index.js [] []} {red check-circle}} DEBU[0001] type=2 actionDir=/home/gabriele/WebstormProjects/pull-request-comment-trigger actionPath= Workdir=/home/gabriele/WebstormProjects/pull-request-comment-trigger ActionCacheDir=/home/gabriele/.cache/act actionName=pull-request-comment-trigger containerActionDir=/github/workspace DEBU[0001] executing remote job container: [node /github/workspace/pull-request-comment-trigger/dist/index.js] [Pull Request Comment Trigger Example/eyes] Exec command '[node /github/workspace/pull-request-comment-trigger/dist/index.js]' | OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "node": executable file not found in $PATH: unknown [Pull Request Comment Trigger Example/eyes] ❌ Failure - ./ DEBU[0001] exit with `FAILURE`: 126 DEBU[0001] exit with `FAILURE`: 126 Error: exit with `FAILURE`: 126 </details>
kerem 2026-03-01 21:44:01 +03:00
kerem commented 2026-03-01 21:44:02 +03:00
Author
Owner
Copy link

@GabrieleCalarota commented on GitHub (Oct 6, 2021):

@catthehacker Very annoying this though. It worked the first time, than never worked again (I reinstalled act and docker few times)

<!-- gh-comment-id:936512241 --> @GabrieleCalarota commented on GitHub (Oct 6, 2021): @catthehacker Very annoying this though. It worked the first time, than never worked again (I reinstalled act and docker few times)
kerem commented 2026-03-01 21:44:02 +03:00
Author
Owner
Copy link

@catthehacker commented on GitHub (Oct 7, 2021):

Please follow the template.

<!-- gh-comment-id:937599882 --> @catthehacker commented on GitHub (Oct 7, 2021): Please follow the template.
kerem commented 2026-03-01 21:44:02 +03:00
Author
Owner
Copy link

@GabrieleCalarota commented on GitHub (Oct 7, 2021):

Update, please reopen. I followed the template and gave every details I have. Issue should be reproducible now and seems very clear to me what's wrong, I have no clue how to fix it @catthehacker

<!-- gh-comment-id:937886534 --> @GabrieleCalarota commented on GitHub (Oct 7, 2021): Update, please reopen. I followed the template and gave every details I have. Issue should be reproducible now and seems very clear to me what's wrong, I have no clue how to fix it @catthehacker
kerem commented 2026-03-01 21:44:02 +03:00
Author
Owner
Copy link

@ChristopherHX commented on GitHub (Oct 7, 2021):

act version: 0.3.2

Thats odd, this version of act isn't even released yet (act still has version 0.2.x)

Please follow the template and provide the full log, not only the part you provided. Your provided log is missing the important part of the log, e.g. which docker image it used to ran your steps.

Use act with -v/--verbose and paste output from your terminal in code block below

act requires that the executing docker image has node installed and in $PATH, unlike actions/runner which doesn't require it.

Also which commandline did you use to run act?
act ...

It isn't common to ping a maintainer within 24h after opening an issue

<!-- gh-comment-id:938176808 --> @ChristopherHX commented on GitHub (Oct 7, 2021): > act version: 0.3.2 Thats odd, this version of act isn't even released yet (act still has version 0.2.x) Please follow the template and provide the **full** log, not only the part you provided. Your provided log is missing the important part of the log, e.g. which docker image it used to ran your steps. > Use `act` with `-v`/`--verbose` and paste output from your terminal in code block below **act requires that the executing docker image has node installed and in `$PATH`**, unlike actions/runner which doesn't require it. Also which commandline did you use to run act? `act ...` _It isn't common to ping a maintainer within 24h after opening an issue_
kerem commented 2026-03-01 21:44:02 +03:00
Author
Owner
Copy link

@GabrieleCalarota commented on GitHub (Oct 8, 2021):

act requires that the executing docker image has node installed and in $PATH, unlike actions/runner which doesn't require it.

How do I do this? There's no doc in the README.md about this!
I think this is the key point here, I've looked on google. I have no clue on this.

Also which commandline did you use to run act?
act ...

act -v issue_comment

Thats odd, this version of act isn't even released yet (act still has version 0.2.x)

Updated 0.2.14

Can you please reopen now?

<!-- gh-comment-id:938418962 --> @GabrieleCalarota commented on GitHub (Oct 8, 2021): > **act requires that the executing docker image has node installed and in `$PATH`**, unlike actions/runner which doesn't require it. How do I do this? There's no doc in the README.md about this! I think this is the key point here, I've looked on google. I have no clue on this. > Also which commandline did you use to run act? > `act ...` `act -v issue_comment` > Thats odd, this version of act isn't even released yet (act still has version 0.2.x) Updated 0.2.14 Can you please reopen now?
kerem commented 2026-03-01 21:44:02 +03:00
Author
Owner
Copy link

@ChristopherHX commented on GitHub (Oct 8, 2021):

Hmm, catthehacker/ubuntu:act-latest should contain node out of box.

How do I do this?

After reading your full log, the image should work without changes. Only if you use a custom image you need to install node yourself, but you are using a default image.

There's no doc in the README.md about this!

You are correct

Maybe try updating the image. I think act keeps using a broken image version. I doubt I will be able to reproduce this without the output of docker images on your system.

docker pull catthehacker/ubuntu:act-latest

Then run act again. I never had such a problem.

Can you please reopen now?

I don't have the permission to do that.

<!-- gh-comment-id:938755784 --> @ChristopherHX commented on GitHub (Oct 8, 2021): Hmm, `catthehacker/ubuntu:act-latest` should contain `node` out of box. > How do I do this? After reading your full log, the image should work without changes. Only if you use a custom image you need to install node yourself, but you are using a default image. > There's no doc in the README.md about this! You are correct Maybe try updating the image. I think act keeps using a broken image version. I doubt I will be able to reproduce this without the output of `docker images` on your system. ``` docker pull catthehacker/ubuntu:act-latest ``` Then run act again. I never had such a problem. > Can you please reopen now? I don't have the permission to do that.
kerem commented 2026-03-01 21:44:02 +03:00
Author
Owner
Copy link

@catthehacker commented on GitHub (Oct 9, 2021):

Current act release is v0.2.24 (https://github.com/nektos/act/releases/tag/v0.2.24)
I recommend using latest version since each version we fix a lot of issues and improve experience
Latest versions for available package managers can be seen in README.md

<!-- gh-comment-id:939268970 --> @catthehacker commented on GitHub (Oct 9, 2021): Current act release is v0.2.24 (https://github.com/nektos/act/releases/tag/v0.2.24) I recommend using latest version since each version we fix a lot of issues and improve experience Latest versions for available package managers can be seen in [README.md](https://github.com/nektos/act/blob/master/README.md)
kerem commented 2026-03-01 21:44:02 +03:00
Author
Owner
Copy link

@GabrieleCalarota commented on GitHub (Oct 10, 2021):

Hmm, catthehacker/ubuntu:act-latest should contain node out of box.

How do I do this?

After reading your full log, the image should work without changes. Only if you use a custom image you need to install node yourself, but you are using a default image.

There's no doc in the README.md about this!

You are correct

Maybe try updating the image. I think act keeps using a broken image version. I doubt I will be able to reproduce this without the output of docker images on your system.

docker pull catthehacker/ubuntu:act-latest

Then run act again. I never had such a problem.

Can you please reopen now?

I don't have the permission to do that.

Thanks, it worked pulling again the image.

Anyway this is the output of docker images

gabriele@gabriele-pc:~/WebstormProjects/pull-request-comment-trigger$ docker images
REPOSITORY                       TAG          IMAGE ID       CREATED         SIZE
catthehacker/ubuntu              act-latest   d0ec3129d673   27 hours ago    992MB
catthehacker/ubuntu              <none>       fffe252cee37   8 days ago      992MB
catthehacker/ubuntu              act-18.04    ddbaca8ce149   8 days ago      869MB
node                             12-buster    7b43a635a11e   12 days ago     886MB
node                             latest       9c23a8242f8b   12 days ago     908MB
<none>                           <none>       9b0e189a712d   10 months ago   132MB
<none>                           <none>       5cd65fd18890   10 months ago   132MB
<none>                           <none>       77ef2e72ebc0   10 months ago   132MB
<none>                           <none>       9ec625867680   10 months ago   132MB
<none>                           <none>       056f52b5b2fe   10 months ago   132MB
<none>                           <none>       3062363ae5b1   10 months ago   132MB
<none>                           <none>       c06e5ba66a0d   10 months ago   132MB
<none>                           <none>       db05d6a7ecbb   10 months ago   132MB
<none>                           <none>       af41db30ec41   10 months ago   132MB
node                             10-alpine    b328632eb00c   11 months ago   83.6MB
nektos/act-environments-ubuntu   18.04        8aaea77c344b   19 months ago   18.2GB
hello-world                      latest       bf756fb1ae65   21 months ago   13.3kB
<!-- gh-comment-id:939470809 --> @GabrieleCalarota commented on GitHub (Oct 10, 2021): > Hmm, `catthehacker/ubuntu:act-latest` should contain `node` out of box. > > > How do I do this? > > After reading your full log, the image should work without changes. Only if you use a custom image you need to install node yourself, but you are using a default image. > > > There's no doc in the README.md about this! > > You are correct > > Maybe try updating the image. I think act keeps using a broken image version. I doubt I will be able to reproduce this without the output of `docker images` on your system. > > ``` > docker pull catthehacker/ubuntu:act-latest > ``` > > Then run act again. I never had such a problem. > > > Can you please reopen now? > > I don't have the permission to do that. Thanks, it worked pulling again the image. Anyway this is the output of `docker images` ``` gabriele@gabriele-pc:~/WebstormProjects/pull-request-comment-trigger$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE catthehacker/ubuntu act-latest d0ec3129d673 27 hours ago 992MB catthehacker/ubuntu <none> fffe252cee37 8 days ago 992MB catthehacker/ubuntu act-18.04 ddbaca8ce149 8 days ago 869MB node 12-buster 7b43a635a11e 12 days ago 886MB node latest 9c23a8242f8b 12 days ago 908MB <none> <none> 9b0e189a712d 10 months ago 132MB <none> <none> 5cd65fd18890 10 months ago 132MB <none> <none> 77ef2e72ebc0 10 months ago 132MB <none> <none> 9ec625867680 10 months ago 132MB <none> <none> 056f52b5b2fe 10 months ago 132MB <none> <none> 3062363ae5b1 10 months ago 132MB <none> <none> c06e5ba66a0d 10 months ago 132MB <none> <none> db05d6a7ecbb 10 months ago 132MB <none> <none> af41db30ec41 10 months ago 132MB node 10-alpine b328632eb00c 11 months ago 83.6MB nektos/act-environments-ubuntu 18.04 8aaea77c344b 19 months ago 18.2GB hello-world latest bf756fb1ae65 21 months ago 13.3kB ````
kerem commented 2026-03-01 21:44:03 +03:00
Author
Owner
Copy link

@catthehacker commented on GitHub (Oct 11, 2021):

So everything works now?

<!-- gh-comment-id:939594040 --> @catthehacker commented on GitHub (Oct 11, 2021): So everything works now?
kerem commented 2026-03-01 21:44:03 +03:00
Author
Owner
Copy link

@GabrieleCalarota commented on GitHub (Oct 12, 2021):

So everything works now?

Yes thank you, as @ChristopherHX suggested the image was broken, I had to pull it again

Issue can be closed now @catthehacker

I'll take advantage, I've seen there's no discussion panel here, where can I ask a question? Should I open another issue?
I would like to know how to print logs of variables in a custom actions running it locally with act

<!-- gh-comment-id:940778179 --> @GabrieleCalarota commented on GitHub (Oct 12, 2021): > So everything works now? Yes thank you, as @ChristopherHX suggested the image was broken, I had to pull it again Issue can be closed now @catthehacker I'll take advantage, I've seen there's no discussion panel here, where can I ask a question? Should I open another issue? I would like to know how to print logs of variables in a custom actions running it locally with act
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dependabot/go_modules/github.com/go-git/go-git/v5-5.18.0
dependabot/go_modules/dependencies-08815e2262
mergify/configuration-deprecated-update
dependabot/github_actions/dependencies-a3a104477f
chore/simplify-ci-and-makefile
dependabot/go_modules/golang.org/x/crypto-0.45.0
dependabot/go_modules/github.com/go-viper/mapstructure/v2-2.4.0
panekj/ci/improve-jobs
fix-skip-non-yaml-files-in-dir
normalize-pull-rebuild-flags
fix-no-recurse-by-default
2517-poor-error-for-incomplete-action-step
2472-make-use-new-action-cache-the-new-default-for-downloading-actions
act-tart
act-lxc
act-oidc
act-dind
avoid-slash-in-actor
dependabot/go_modules/github.com/docker/docker-26.1.4incompatible
meta-keep-filetime
local-repository-action-cache
pr-merger
update-docker-deps
follow_local_action_symlink
boltdb-lock-in-handler
use-socket-path
no-pull-no-rebuild
path-issues
fix/env
feat/podman
refactor/testdata
v0.2.87
v0.2.86
v0.2.85
v0.2.84
v0.2.83
v0.2.82
v0.2.81
v0.2.80
v0.2.79
v0.2.78
v0.2.77
v0.2.76
v0.2.75
v0.2.74
v0.2.73
v0.2.72
v0.2.71
v0.2.70
v0.2.69
v0.2.68
v0.2.67
v0.2.66
v0.2.65
v0.2.64
v0.2.63
v0.2.62
v0.2.61
v0.2.60
v0.2.59
v0.2.58
v0.2.57
v0.2.56
v0.2.55
v0.2.54
v0.2.53
v0.2.52
v0.2.51
v0.2.50
v0.2.49
v0.2.48
v0.2.47
v0.2.46
v0.2.45
v0.2.44
v0.2.43
v0.2.42
v0.2.41
v0.2.40
v0.2.39
v0.2.38
v0.2.37
v0.2.36
v0.2.35
v0.2.34
v0.2.33
v0.2.32
v0.2.31
v0.2.30
v0.2.29
v0.2.28
v0.2.27
v0.2.26
v0.2.25
v0.2.24
v0.2.23
v0.2.22
v0.2.21
v0.2.20
v0.2.19
v0.2.18
v0.2.17
v0.2.16
v0.2.15
v0.2.14
v0.2.13
v0.2.12
v0.2.11
v0.2.10
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.3
v0.1.2
v0.1.1
v0.1.0
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels   
area/action

   
area/cli

   
area/docs

   
area/image

   
area/runner

   
area/workflow

   
backlog

   
confirmed/not-planned

   
kind/bug

   
kind/discussion

   
kind/external

   
kind/feature-request

   
kind/question

   
meta/duplicate

   
meta/invalid

   
meta/need-more-info

   
meta/resolved

   
meta/wontfix

   
meta/workaround

   
needs-work

   
pull-request

Mirrored from GitHub Pull Request

  
review/not-planned

   
size/M

   
size/XL

   
size/XXL

   
stale

   
stale-exempt
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#507
No description provided.