Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    Crazy question maybe, but has anyone thought about running act on fly.io ?
    Please don't
    Jasper Nygaard
    Hi all. I'm trouble shooting an issue where I use OctopusDeploy/install-octopus-cli-action in a workflow, but get the error 'Error: reference delta not found' when running with act. Anyone seen this error before?
    Shashwat Arghode

    Hi All,
    I am a new ACT user struggling to run the following CI job locally. Any help is appreciated.
    CI job: https://github.com/prestodb/presto/blob/master/.github/workflows/ci.yml
    Command: act -v

    DEBU[0000] Loading environment from /Users/sarghode/IdeaProjects/prestodb/.env 
    DEBU[0000] Loading secrets from /Users/sarghode/IdeaProjects/prestodb/.secrets 
    DEBU[0000] Loading workflows from '/Users/sarghode/IdeaProjects/prestodb/.github/workflows' 
    DEBU[0000] Loading workflows recursively                
    DEBU[0000] Found workflow 'ci.yml' in '/Users/sarghode/IdeaProjects/prestodb/.github/workflows/ci.yml' 
    DEBU[0000] Found workflow 'cleanup.yml' in '/Users/sarghode/IdeaProjects/prestodb/.github/workflows/cleanup.yml' 
    DEBU[0000] Reading workflow '/Users/sarghode/IdeaProjects/prestodb/.github/workflows/ci.yml' 
    DEBU[0000] Correcting if statements '/Users/sarghode/IdeaProjects/prestodb/.github/workflows/ci.yml' 
    DEBU[0000] Reading workflow '/Users/sarghode/IdeaProjects/prestodb/.github/workflows/cleanup.yml' 
    DEBU[0000] Correcting if statements '/Users/sarghode/IdeaProjects/prestodb/.github/workflows/cleanup.yml' 
    DEBU[0000] Planning event: push

    It crashes after this setup without any error log.


    3 replies
    Mathijs van Veluw
    Hello there, I have a question regarding docker images build during an act run. When using docker/setup-buildx-action and docker/build-push-action the build images do not seem to appear in my local image list when checking docker image list is there a way to have this working?
    1 reply
    Mathijs van Veluw
    Seems setup-buildx-action is doing something to mess with the local images
    if i use DOCKER_BUILDKIT=1 instead it works, so i will just do some if: env.ACT checking :)
    If someone has a better idea or solution, please share :).
    Isaac Guerreiro
    Hello, everyone. I'm trying to run locally my action, but didn't work. `jobs:
    runs-on: self-hosted
    contents: read
    packages: write
    image: mcr.microsoft.com/vscode/devcontainers/base:ubuntu
    options: --user 1001
    - uses: actions/checkout@v2
    - name: Run action
      uses: ./`
    2 replies
    Anyone know how I could run this locally.
    Colin Alworth
    i'm seeing a difference in behavior between ghcr.io/catthehacker/ubuntu:act-latest and ghcr.io/catthehacker/ubuntu:full-latest when running actions/checkout@v2 with a with:path: specified - act-latest behaves as expected and the layout makes sense, but full-latest gets permission errors when trying to set things up. Where would be the best place to file this?
    3 replies
    Mohsin Hijazee

    I have this args for an action and the "Expressions" don't seem to work

     name: Fetch environment variables from AWS Parameter Store
          uses: classtinginc/chamber-action@master
          id: chamber
            args: export --format dotenv --output-file parameters.env ${{ env.SERVICE_NAME }}

    So instead of the variable SERVICE_NAME being injected, the literal ${{ is being injected. Any ideas?

    1 reply

    Hi everyone. I'm using act to locally test my github action to create minikube cluster. This is the code I have for this task.
    name: Minikube deploy

      - master

    runs-on: ubuntu-latest

      - name: Install minikube
        run: |
          sudo curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64
          sudo install minikube-linux-amd64 /usr/local/bin/minikube
      - uses: yokawasa/action-setup-kube-tools@v0.7.1
          setup-tools: kubectl
          kubectl: '1.18.18'
      - name: Add user
        run: |
          getent group sudo
          getent group docker
          echo $USER
          sudo usermod -aG docker $USER
          getent group docker
          sudo chmod 666 /var/run/docker.sock
          echo "hi"
      - name: Start minikube
        run: |
          sudo minikube delete
          minikube start
          kubectl get pods -A
          echo "end"

    The "Add user" part is me trying to give docker non root user so that docker commands could be run. Ubuntu image used is ubuntu-latest=ghcr.io/catthehacker/ubuntu:runner-latest
    Everything is running fine until this next line which is part of minikube start command and then it freezes.
    Downloading Kubernetes v1.22.2 preload ...

    > preloaded-images-k8s-v13-v1...: 511.84 MiB / 511.84 MiB  100.00% 14.22 Mi

    If I add --alsologtostderr I get this type of error on the same part of running process.
    libmachine: Error dialing TCP: dial tcp connect: connection refused
    So the problem is I can't create minikube cluster with act. Does anyone know what is the cause of this errors ?

    Eduardo Robles
    Hello! how can I add more RAM to act runner?
    4 replies
    hi! just found this repo today and had a question. i am using it with a private npm registry and get UNABLE_TO_GET_ISSUER_CERT_LOCALLY as an error. does anyone know how to bypass this?
    2 replies
    Timothy J Laurent

    I'm seeing

    | OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "node": executable file not found in $PATH: unknown

    when I try to run the checkout action

    Timothy J Laurent

    How can I tell what running act is using?

    my workflow runs-on

        runs-on: [self-hosted, dev]

    And I have

    -P self-hosted=ghcr.io/catthehacker/ubuntu:act-20.04 -P dev=ghcr.io/catthehacker/ubuntu:act-20.04

    in my ~/.actrc

    ^ does that all look right?

    Timothy J Laurent
    So I was using a "Container" argument and it looks like ACT will use that instead of the runners.
    So I cleared that up and added a GITHUB_TOKEN that was going great until I tried to run a docker container action and it couldn't find java
    Szymon Nowak

    Hi! I've got an issue with a running a local action. I've got a local Dockerfile, so in my workflow I've got uses: ./, which causes act to generate an invalid tag for Docker build command (i.e. act-:latest):

    docker build -t act-:latest --platform  /Users/...

    Is there any workaround for this?

    1 reply
    Timothy J Laurent

    Turns out that the ~/.actrc / ./.actrc needs to be one parameter per line.

    -P self-hosted=ghcr.io/catthehacker/ubuntu:act-20.04
    -P dev=ghcr.io/catthehacker/ubuntu:act-20.04

    Maybe I'm confusing the issues I had with the container: param?

    So here's a summary of the issues I've encountered.

    • Using the container parameter will override whatever is in the runs-on
    • Docker-based actions aren't working - eg java not found on JVM image.
    Error: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "java": executable file not found in $PATH: unknown

    Is there some way to enable these features on Act?

    2 replies
    Tomasz Dłuski

    Is it possible to run node14 in act? I can only see node12 images. When running some yarn cli ive got following error

    Publish in Chrome Web Store/publish] ⭐  Run Install chrome web store cli
    yarn global v1.22.5
    warning package.json: No license field
    [1/4] Resolving packages...
    [2/4] Fetching packages...
    error chrome-webstore-upload-cli@2.0.1: The engine "node" is incompatible with this module. Expected version "^14.13.1 || >=16.0.0". Got "12.20.1"
    error Found incompatible module.
    info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.
    [Publish in Chrome Web Store/publish]   ❌  Failure - Install chrome web store cli

    but I do have

    - name: Use Node.js ${{ matrix.node-version }}
          uses: actions/setup-node@v2
            node-version: 14.x
    2 replies
    I want to get off github but still use my workflows . What i dont see is how i can do builds on wi diws mac and linux cause the Act system currentky uses Docker . Am i missing something ?? ?
    1 reply
    Josh Soref
    when I try to run make in nektos/act, I get a bunch of build failures, is that expected? :-(
    1 reply
    especially github/super-linter (action-linter / shellcheck) seems to hate .github/workflows/checks.yml -- and while I can fix some of the complaints, I can't fix all of them
    Also, for reasons... the PATH var appears to be quite buggy in the tests https://www.irccloud.com/pastebin/jhdROhkM/
    1 reply
    jsoref @jsoref stubs foot on fmt.Printf or some relative https://www.irccloud.com/pastebin/S0q05GtQ/
    Kingdon Barrett
    Greetings, I am trying to understand why my github actions workflow does not work in act and so far I've tried a few things. I got to the point where RUNNER_WORKSPACE is raised as an undefined variable since my action includes it in an entrypoint.sh, and I was searching for the meaning of that variable and came up somewhat empty on understanding.
    So far I have figured out that since my action writes back to the GITHUB_WORKSPACE, I need to start act with -b for bind mode instead of copy, else I get Permission Denied creating the "bin" dir. I tried changing the script entrypoint.sh to just don't call RUNNER_WORKSPACE anymore, and it didn't seem to have any effect.
    Colin Alworth
    @kingdonb share your command/yml? (i know there is a permission denied issue with the full-latest tagged image)
    (I have messed with the actions/tools in some ways that I think haven't helped in the main branch, this is the original "actions/tools")
    I'm using act compiled from the main branch today
    Colin Alworth
    what is your act command/configs?
    Kingdon Barrett
    ~/go/bin/act -b --privileged
    3 replies
    Kingdon Barrett
    ~/.actrc looks like it was generated, it is the defaults:
    -P ubuntu-latest=catthehacker/ubuntu:act-latest
    -P ubuntu-20.04=catthehacker/ubuntu:act-20.04
    -P ubuntu-18.04=catthehacker/ubuntu:act-18.04
    are there any caches which I can clean if it looks like my latest changes in current directory are for some reason not reflected in the running act behavior
    5 replies
    Kingdon Barrett
    (line 28 no longer refers to RUNNER_WORKSPACE but I still get:
    | /entrypoint.sh: line 28: RUNNER_WORKSPACE: unbound variable)
    Szymon Nowak
    Hi! I got a question related to unbound variable error as well. If in my action.yml file I've got an input defined with a default value (e.g. called min_score), should there be an environment variable INPUT_MIN_SCORE that is set to this default value available in entrypoint.sh file? Because I'm getting unbound variable errors in this case. I'm not sure if it's how GH actions work or if it's a bug in act itself.
    Callum Tait
    hello people, I have an error using act which is happening because the container I am using in my workflow does not have bash, it's na alpine image
    I think anyway
    my workflow looks like:
    name: Lint Actions workflows
          - .github/workflows/*.yaml
        runs-on: ubuntu-latest
          image: rhysd/actionlint:latest
          args: --entrypoint sh
          - name: Run lint
            run: |
              echo "::add-matcher::.github/actionlint-matcher.json"
              for file in .github/workflows/*.yaml; do 
                  if [ -f "$file" ]; then
                    actionlint -color $file
    and my act after issuing act pull_request -j lint I get the error:
    [Lint Actions workflows/lint]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /Users/user/git/work/owner/terraform-template-repository/master/workflow/0] user=
    [Lint Actions workflows/lint] Exec command '[bash --noprofile --norc -e -o pipefail /Users/user/git/work/owner/terraform-template-repository/master/workflow/0]'
    | OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "bash": executable file not found in $PATH: unknown
    DEBU[0000] exit with `FAILURE`: 126
    Callum Tait
    yeh, if I remove the container and do it directly in the image then the failed to find bash disappears
    2 replies
    Markus Wolf
    Hi there,
    would it be possible to have more contributors with write access to act? Currently the project feels a bit limited by the time available to review and merge PRs.
    23 replies
    Erik Brown

    I'm using act 0.2.24 and it appears not to copy the repo. Here is a simple workflow that reproduces this:

    name: "Test that local file exists"
        runs-on: ubuntu-latest
          - uses: actions/checkout@v2
          - name: Make sure requirements.txt exists
            run: ls requirements.txt

    This gives an error ls: cannot access 'requirements.txt': No such file or directory. I found a similar thread that suggested using act -P ubuntu-latest=shivammathur/node:latest but this produced the same result. I can add a with statement to the check to get the full repo and then this works. However, I'm making local changes so I really want to use my local repo. Any suggestions or workarounds?

    14 replies
    Martin K. Scherer
    Hi, just installed git version via AUR on Arch and getting a "zero" value error directly after choosing the image. I've searched the issue list on Github and there was a similar error, but in a submenu. This seems to affect the whole image selection thing. Should I just go a head and create a new issue, or does somebody here want to take a look at some logs first?
    1 reply
    I can only reproduce this in a certain repo containing a more or less complex matrix. Eventually this is the cause. Is it fine to reference this repo/commit hash in the issue or should I try to identify a minimum "working" example?
    1 reply