From 360282b6f41f3c1a90598bcb41ca57f7478fc9b9 Mon Sep 17 00:00:00 2001 From: Dave Tapley Date: Tue, 6 Jul 2021 22:20:32 -0700 Subject: [PATCH 1/3] Add docker context workaround to readme --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index 22c3957ff43..2eb0b407ad2 100644 --- a/README.md +++ b/README.md @@ -188,6 +188,17 @@ steps: If the `path:` value doesn't match the name of the repository, a `MODULE_NOT_FOUND` will be thrown. +## `docker context` support + +The current `docker context` isn't respected ([#583](https://github.com/nektos/act/issues/583)). + +You can work around this by setting `DOCKER_HOST` before running `act`, with e.g: + +```bash +export DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}') +``` + + # Runners GitHub Actions offers managed [virtual environments](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners) for running workflows. In order for `act` to run your workflows locally, it must run a container for the runner defined in your workflow file. Here are the images that `act` uses for each runner type and size: From 83c08d261bc878f12bc5355dd93501d1d3aed2fa Mon Sep 17 00:00:00 2001 From: Dave Tapley Date: Wed, 7 Jul 2021 07:26:41 -0700 Subject: [PATCH 2/3] Update README.md Co-authored-by: Ryan (hackercat) --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index 2eb0b407ad2..f751a6eaf1e 100644 --- a/README.md +++ b/README.md @@ -197,8 +197,6 @@ You can work around this by setting `DOCKER_HOST` before running `act`, with e.g ```bash export DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}') ``` - - # Runners GitHub Actions offers managed [virtual environments](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners) for running workflows. In order for `act` to run your workflows locally, it must run a container for the runner defined in your workflow file. Here are the images that `act` uses for each runner type and size: From 3b56a137202e1e4cc3f9ce8037c031a1ddcd1c2e Mon Sep 17 00:00:00 2001 From: Dave Tapley Date: Wed, 7 Jul 2021 08:34:06 -0700 Subject: [PATCH 3/3] Fix README MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [ --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index f751a6eaf1e..984c0c4e795 100644 --- a/README.md +++ b/README.md @@ -197,6 +197,7 @@ You can work around this by setting `DOCKER_HOST` before running `act`, with e.g ```bash export DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}') ``` + # Runners GitHub Actions offers managed [virtual environments](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners) for running workflows. In order for `act` to run your workflows locally, it must run a container for the runner defined in your workflow file. Here are the images that `act` uses for each runner type and size: