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 #583] Issue: Got error when use act at locally with remote docker contexts #388

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

Originally created by @Aisuko on GitHub (Mar 25, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/583

Act version

➜  helm-charts-action git:(master) ✗ act --version
act version 0.2.20

Expected behaviour

act can work well with remote docker context, and I can pull the target image by manually.

Actual behaviour

act can not pull the image

Workflow and/or repository

workflow 
name: Release Charts

on:
  push:
    branches:
      - master
  workflow_dispatch:
    inputs:
      logLevel:
        description: 'Log level'
        required: true
        default: 'warning'

jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
        with:
          fetch-depth: 0

      - name: Configure Git
        run: |
          git config user.name "$GITHUB_ACTOR"
          git config user.email "$GITHUB_ACTOR@users.noreply.github.com"

      - name: Install Helm
        uses: azure/setup-helm@v1
        with:
          version: v3.4.1

      # Optional step if GPG signing is used
      # - name: Prepare GPG key
      #   run: |
      #     gpg_dir=.cr-gpg
      #     mkdir "$gpg_dir"

      #     keyring="$gpg_dir/secring.gpg"
      #     base64 -d <<< "$GPG_KEYRING_BASE64" > "$keyring"

      #     passphrase_file="$gpg_dir/passphrase"
      #     echo "$GPG_PASSPHRASE" > "$passphrase_file"

      #     echo "CR_PASSPHRASE_FILE=$passphrase_file" >> "$GITHUB_ENV"
      #     echo "CR_KEYRING=$keyring" >> "$GITHUB_ENV"
      #   env:
      #     GPG_KEYRING_BASE64: "${{ secrets.GPG_KEYRING_BASE64 }}"
      #     GPG_PASSPHRASE: "${{ secrets.GPG_PASSPHRASE }}"

      - name: Add dependency chart repos
        run: |
          helm repo add meshery https://meshery.io/charts/

      - name: Helm Chart Releaser For Remote
        uses: Aisuko/chart-releaser-action@v1.0.0-alpha.4
        with:
          charts_dir: install
          owner: Aisuko
          repo: charts-release
          # For helm charts index
          charts_repo_url: https://aisuko.github.io/charts-release
        env:
          CR_TOKEN: "${{ secrets.TOKEN }}"

Steps to reproduce

act output

Log 
➜  helm-charts-action git:(master) ✗ act -n -v
DEBU[0000] Loading environment from /Users/peasant/Documents/helm-charts-action/.env
DEBU[0000] Loading secrets from /Users/peasant/Documents/helm-charts-action/.secrets
DEBU[0000] Loading workflows from '/Users/peasant/Documents/helm-charts-action/.github/workflows'
DEBU[0000] Reading workflow '/Users/peasant/Documents/helm-charts-action/.github/workflows/lint-test.yaml'
DEBU[0000] Reading workflow '/Users/peasant/Documents/helm-charts-action/.github/workflows/release.yaml'
DEBU[0000] Planning event: push
DEBU[0000] Loading slug from git directory '/Users/peasant/Documents/helm-charts-action/.git'
DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e
DEBU[0000] Loading revision from git directory '/Users/peasant/Documents/helm-charts-action/.git'
DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e
DEBU[0000] HEAD points to '296c8e291f2da06b236c92629848fd4663bd3a9e'
DEBU[0000] HEAD matches refs/heads/master
DEBU[0000] using github ref: refs/heads/master
DEBU[0000] context env => map[ACT:true CR_TOKEN:12c8f8fe2e21bd57107357fd0d5b5da665a9711b]
DEBU[0000] Loading slug from git directory '/Users/peasant/Documents/helm-charts-action/.git'
DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e
DEBU[0000] Loading revision from git directory '/Users/peasant/Documents/helm-charts-action/.git'
DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e
DEBU[0000] HEAD points to '296c8e291f2da06b236c92629848fd4663bd3a9e'
DEBU[0000] HEAD matches refs/heads/master
DEBU[0000] using github ref: refs/heads/master
DEBU[0000] context env => map[ACT:true CR_TOKEN:12c8f8fe2e21bd57107357fd0d5b5da665a9711b]
*DRYRUN* [Release Charts/release        ] 🚀  Start image=catthehacker/ubuntu:act-latest
DEBU[0000] Loading slug from git directory '/Users/peasant/Documents/helm-charts-action/.git'
DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e
DEBU[0000] Loading revision from git directory '/Users/peasant/Documents/helm-charts-action/.git'
DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e
DEBU[0000] HEAD points to '296c8e291f2da06b236c92629848fd4663bd3a9e'
DEBU[0000] HEAD matches refs/heads/master
DEBU[0000] using github ref: refs/heads/master
*DRYRUN* [Release Charts/release        ]   🐳  docker pull catthehacker/ubuntu:act-latest
*DRYRUN* [Lint and Test Charts/lint-test] 🚀  Start image=catthehacker/ubuntu:act-latest
DEBU[0000] Loading slug from git directory '/Users/peasant/Documents/helm-charts-action/.git'
DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e
DEBU[0000] Loading revision from git directory '/Users/peasant/Documents/helm-charts-action/.git'
DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e
DEBU[0000] HEAD points to '296c8e291f2da06b236c92629848fd4663bd3a9e'
DEBU[0000] HEAD matches refs/heads/master
DEBU[0000] using github ref: refs/heads/master
*DRYRUN* [Lint and Test Charts/lint-test]   🐳  docker pull catthehacker/ubuntu:act-latest
DEBU[0000] FIXME: Got an status-code for which error does not match any expected type!!!: -1  module=api status_code=-1
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
DEBU[0000] FIXME: Got an status-code for which error does not match any expected type!!!: -1  module=api status_code=-1
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
➜  helm-charts-action git:(master) ✗ docker context ls
NAME            DESCRIPTION                               DOCKER ENDPOINT               KUBERNETES ENDPOINT   ORCHESTRATOR
default         Current DOCKER_HOST based configuration   unix:///var/run/docker.sock                         swarm
redthirteen *   redthirteen                               ssh://aisuko@192.168.1.104
➜  helm-charts-action git:(master) ✗ docker images
REPOSITORY                                                      TAG                                        IMAGE ID       CREATED         SIZE
catthehacker/ubuntu                                             act-latest                                 516a91a01868   2 days ago      528MB
sickcodes/docker-osx                                            big-sur                                    a32a578a260a   5 days ago      3.25GB
<none>                                                          <none>                                     c14679285dd2   9 days ago      815MB
<none>                                                          <none>                                     d6b4fd464b03   9 days ago      815MB
vsc-mit-scheme-a3ad0cd28c253fbef4b418939bae5d95-uid             latest                                     5836980029e7   2 weeks ago     711MB
vsc-mit-scheme-a3ad0cd28c253fbef4b418939bae5d95                 latest                                     692f54af05cc   2 weeks ago     711MB
<none>                                                          <none>                                     261c7901ecab   4 weeks ago     711MB
vsc-mit-gnu-scheme-f8156c18abdddf4975e24318610814dd             latest                                     b45be34c65db   4 weeks ago     711MB
Originally created by @Aisuko on GitHub (Mar 25, 2021). Original GitHub issue: https://github.com/nektos/act/issues/583 <!-- - 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). --> ## Act version <!-- Paste output of `act --version` --> ```none ➜ helm-charts-action git:(master) ✗ act --version act version 0.2.20 ``` ## Expected behaviour <!-- Describe how whole process should go and finish --> `act` can work well with remote docker context, and I can pull the target image by manually. ## Actual behaviour `act` can not pull the image <!-- Describe what happened --> ## Workflow and/or repository <details> <summary>workflow</summary> ```none name: Release Charts on: push: branches: - master workflow_dispatch: inputs: logLevel: description: 'Log level' required: true default: 'warning' jobs: release: runs-on: ubuntu-latest steps: - name: Checkout uses: actions/checkout@v2 with: fetch-depth: 0 - name: Configure Git run: | git config user.name "$GITHUB_ACTOR" git config user.email "$GITHUB_ACTOR@users.noreply.github.com" - name: Install Helm uses: azure/setup-helm@v1 with: version: v3.4.1 # Optional step if GPG signing is used # - name: Prepare GPG key # run: | # gpg_dir=.cr-gpg # mkdir "$gpg_dir" # keyring="$gpg_dir/secring.gpg" # base64 -d <<< "$GPG_KEYRING_BASE64" > "$keyring" # passphrase_file="$gpg_dir/passphrase" # echo "$GPG_PASSPHRASE" > "$passphrase_file" # echo "CR_PASSPHRASE_FILE=$passphrase_file" >> "$GITHUB_ENV" # echo "CR_KEYRING=$keyring" >> "$GITHUB_ENV" # env: # GPG_KEYRING_BASE64: "${{ secrets.GPG_KEYRING_BASE64 }}" # GPG_PASSPHRASE: "${{ secrets.GPG_PASSPHRASE }}" - name: Add dependency chart repos run: | helm repo add meshery https://meshery.io/charts/ - name: Helm Chart Releaser For Remote uses: Aisuko/chart-releaser-action@v1.0.0-alpha.4 with: charts_dir: install owner: Aisuko repo: charts-release # For helm charts index charts_repo_url: https://aisuko.github.io/charts-release env: CR_TOKEN: "${{ secrets.TOKEN }}" ``` </details> ## Steps to reproduce <!-- Make sure to include command you used to run `act` e.g.: 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 <!-- Paste output from your terminal, use `-v` or `--verbose` for richer output --> <details> <summary>Log</summary> ```none ➜ helm-charts-action git:(master) ✗ act -n -v DEBU[0000] Loading environment from /Users/peasant/Documents/helm-charts-action/.env DEBU[0000] Loading secrets from /Users/peasant/Documents/helm-charts-action/.secrets DEBU[0000] Loading workflows from '/Users/peasant/Documents/helm-charts-action/.github/workflows' DEBU[0000] Reading workflow '/Users/peasant/Documents/helm-charts-action/.github/workflows/lint-test.yaml' DEBU[0000] Reading workflow '/Users/peasant/Documents/helm-charts-action/.github/workflows/release.yaml' DEBU[0000] Planning event: push DEBU[0000] Loading slug from git directory '/Users/peasant/Documents/helm-charts-action/.git' DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e DEBU[0000] Loading revision from git directory '/Users/peasant/Documents/helm-charts-action/.git' DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e DEBU[0000] HEAD points to '296c8e291f2da06b236c92629848fd4663bd3a9e' DEBU[0000] HEAD matches refs/heads/master DEBU[0000] using github ref: refs/heads/master DEBU[0000] context env => map[ACT:true CR_TOKEN:12c8f8fe2e21bd57107357fd0d5b5da665a9711b] DEBU[0000] Loading slug from git directory '/Users/peasant/Documents/helm-charts-action/.git' DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e DEBU[0000] Loading revision from git directory '/Users/peasant/Documents/helm-charts-action/.git' DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e DEBU[0000] HEAD points to '296c8e291f2da06b236c92629848fd4663bd3a9e' DEBU[0000] HEAD matches refs/heads/master DEBU[0000] using github ref: refs/heads/master DEBU[0000] context env => map[ACT:true CR_TOKEN:12c8f8fe2e21bd57107357fd0d5b5da665a9711b] *DRYRUN* [Release Charts/release ] 🚀 Start image=catthehacker/ubuntu:act-latest DEBU[0000] Loading slug from git directory '/Users/peasant/Documents/helm-charts-action/.git' DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e DEBU[0000] Loading revision from git directory '/Users/peasant/Documents/helm-charts-action/.git' DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e DEBU[0000] HEAD points to '296c8e291f2da06b236c92629848fd4663bd3a9e' DEBU[0000] HEAD matches refs/heads/master DEBU[0000] using github ref: refs/heads/master *DRYRUN* [Release Charts/release ] 🐳 docker pull catthehacker/ubuntu:act-latest *DRYRUN* [Lint and Test Charts/lint-test] 🚀 Start image=catthehacker/ubuntu:act-latest DEBU[0000] Loading slug from git directory '/Users/peasant/Documents/helm-charts-action/.git' DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e DEBU[0000] Loading revision from git directory '/Users/peasant/Documents/helm-charts-action/.git' DEBU[0000] Found revision: 296c8e291f2da06b236c92629848fd4663bd3a9e DEBU[0000] HEAD points to '296c8e291f2da06b236c92629848fd4663bd3a9e' DEBU[0000] HEAD matches refs/heads/master DEBU[0000] using github ref: refs/heads/master *DRYRUN* [Lint and Test Charts/lint-test] 🐳 docker pull catthehacker/ubuntu:act-latest DEBU[0000] FIXME: Got an status-code for which error does not match any expected type!!!: -1 module=api status_code=-1 DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? DEBU[0000] FIXME: Got an status-code for which error does not match any expected type!!!: -1 module=api status_code=-1 DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? DEBU[0000] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? ➜ helm-charts-action git:(master) ✗ docker context ls NAME DESCRIPTION DOCKER ENDPOINT KUBERNETES ENDPOINT ORCHESTRATOR default Current DOCKER_HOST based configuration unix:///var/run/docker.sock swarm redthirteen * redthirteen ssh://aisuko@192.168.1.104 ➜ helm-charts-action git:(master) ✗ docker images REPOSITORY TAG IMAGE ID CREATED SIZE catthehacker/ubuntu act-latest 516a91a01868 2 days ago 528MB sickcodes/docker-osx big-sur a32a578a260a 5 days ago 3.25GB <none> <none> c14679285dd2 9 days ago 815MB <none> <none> d6b4fd464b03 9 days ago 815MB vsc-mit-scheme-a3ad0cd28c253fbef4b418939bae5d95-uid latest 5836980029e7 2 weeks ago 711MB vsc-mit-scheme-a3ad0cd28c253fbef4b418939bae5d95 latest 692f54af05cc 2 weeks ago 711MB <none> <none> 261c7901ecab 4 weeks ago 711MB vsc-mit-gnu-scheme-f8156c18abdddf4975e24318610814dd latest b45be34c65db 4 weeks ago 711MB ``` </details>
kerem commented 2026-03-01 21:42:57 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (May 3, 2021):

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

<!-- gh-comment-id:830933352 --> @github-actions[bot] commented on GitHub (May 3, 2021): Issue is stale and will be closed in 14 days unless there is new activity
kerem commented 2026-03-01 21:42:57 +03:00
Author
Owner
Copy link

@Aisuko commented on GitHub (May 3, 2021):

@catthehacker I can help test or contribution, please do some feedback

<!-- gh-comment-id:830988346 --> @Aisuko commented on GitHub (May 3, 2021): @catthehacker I can help test or contribution, please do some feedback
kerem commented 2026-03-01 21:42:57 +03:00
Author
Owner
Copy link

@ChristopherHX commented on GitHub (May 3, 2021):

I think act doesn't read docker context configurations, no idea how to do that.

I would try to set the environment variable DOCKER_HOST=ssh://aisuko@192.168.1.104, then act should be able to connect.

DOCKER_HOST=ssh://aisuko@192.168.1.104 act

In the log it tried to connect to localhost, because DOCKER_HOST was set to it's default (or unset) unix:///var/run/docker.sock

<!-- gh-comment-id:831554193 --> @ChristopherHX commented on GitHub (May 3, 2021): I think act doesn't read docker context configurations, no idea how to do that. I would try to set the environment variable `DOCKER_HOST=ssh://aisuko@192.168.1.104`, then act should be able to connect. ```bash DOCKER_HOST=ssh://aisuko@192.168.1.104 act ``` In the log it tried to connect to localhost, because `DOCKER_HOST` was set to it's default (or unset) `unix:///var/run/docker.sock`
kerem commented 2026-03-01 21:42:57 +03:00
Author
Owner
Copy link

@Aisuko commented on GitHub (May 5, 2021):

I think act doesn't read docker context configurations, no idea how to do that.

I would try to set the environment variable DOCKER_HOST=ssh://aisuko@192.168.1.104, then act should be able to connect.

DOCKER_HOST=ssh://aisuko@192.168.1.104 act

In the log it tried to connect to localhost, because DOCKER_HOST was set to it's default (or unset) unix:///var/run/docker.sock

Thanks, I will take it a try.

<!-- gh-comment-id:832573639 --> @Aisuko commented on GitHub (May 5, 2021): > I think act doesn't read docker context configurations, no idea how to do that. > > I would try to set the environment variable `DOCKER_HOST=ssh://aisuko@192.168.1.104`, then act should be able to connect. > > ```shell > DOCKER_HOST=ssh://aisuko@192.168.1.104 act > ``` > > In the log it tried to connect to localhost, because `DOCKER_HOST` was set to it's default (or unset) `unix:///var/run/docker.sock` Thanks, I will take it a try.
kerem commented 2026-03-01 21:42:57 +03:00
Author
Owner
Copy link

@catthehacker commented on GitHub (May 5, 2021):

Docker contexts are not supported and it's quite easy to overcome that (example above). Anyone can feel free to make PR with such feature but it won't be actively pursued.

<!-- gh-comment-id:832924775 --> @catthehacker commented on GitHub (May 5, 2021): Docker contexts are not supported and it's quite easy to overcome that (example above). Anyone can feel free to make PR with such feature but it won't be actively pursued.
kerem commented 2026-03-01 21:42:57 +03:00
Author
Owner
Copy link

@davetapley commented on GitHub (Jun 1, 2021):

Here are one liners to set DOCKER_HOST automatically from current context:

bash:

export DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}')

pwsh:

$env:DOCKER_HOST = (docker context inspect --format '{{.Endpoints.docker.Host}}')
<!-- gh-comment-id:852285247 --> @davetapley commented on GitHub (Jun 1, 2021): Here are one liners to set `DOCKER_HOST` automatically from current `context`: `bash`: ```bash export DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}') ``` `pwsh`: ```pwsh $env:DOCKER_HOST = (docker context inspect --format '{{.Endpoints.docker.Host}}') ```
kerem commented 2026-03-01 21:42:57 +03:00
Author
Owner
Copy link

@Aisuko commented on GitHub (Jun 2, 2021):

I believe we can add these to the README.md as tips, simpler for using is enough.

<!-- gh-comment-id:852631967 --> @Aisuko commented on GitHub (Jun 2, 2021): I believe we can add these to the `README.md` as tips, simpler for using is enough.
kerem commented 2026-03-01 21:42:57 +03:00
Author
Owner
Copy link

@Aisuko commented on GitHub (Jun 15, 2021):

In fact, I'd like to add these to the .env file.

<!-- gh-comment-id:861110302 --> @Aisuko commented on GitHub (Jun 15, 2021): In fact, I'd like to add these to the `.env` file.
kerem commented 2026-03-01 21:42:57 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Jul 16, 2021):

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

<!-- gh-comment-id:881084328 --> @github-actions[bot] commented on GitHub (Jul 16, 2021): Issue is stale and will be closed in 14 days unless there is new activity
kerem commented 2026-03-01 21:42:58 +03:00
Author
Owner
Copy link

@Aisuko commented on GitHub (Jul 16, 2021):

We can close this issue due to #749

<!-- gh-comment-id:881121022 --> @Aisuko commented on GitHub (Jul 16, 2021): We can close this issue due to #749
kerem commented 2026-03-01 21:42:58 +03:00
Author
Owner
Copy link

@luckydonald commented on GitHub (Jan 29, 2024):

Is this meant to be a workaround forever?

<!-- gh-comment-id:1913778526 --> @luckydonald commented on GitHub (Jan 29, 2024): Is this meant to be a workaround forever?
kerem commented 2026-03-01 21:42:58 +03:00
Author
Owner
Copy link

@buahaha commented on GitHub (Aug 17, 2024):

Using podman installed with Homebrew on macOS you can simply follow the instructions during:

podman machine start // this will show the optional helper installation command
podman machine stop
sudo /opt/homebrew/Cellar/podman/5.1.2/bin/podman-mac-helper install

Now you can use it like it's Docker with act 🚀

<!-- gh-comment-id:2294598524 --> @buahaha commented on GitHub (Aug 17, 2024): Using `podman` installed with __Homebrew__ on _macOS_ you can simply follow the instructions during: ```sh podman machine start // this will show the optional helper installation command podman machine stop sudo /opt/homebrew/Cellar/podman/5.1.2/bin/podman-mac-helper install ``` Now you can use it like it's `Docker` 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#388
No description provided.