From 73b22a0da6c442d147a004ae95b732ad7db35584 Mon Sep 17 00:00:00 2001 From: Dave Tapley Date: Wed, 7 Jul 2021 11:41:23 -0700 Subject: [PATCH] Add docker context workaround to readme (#749) * Add docker context workaround to readme * Update README.md Co-authored-by: Ryan (hackercat) * Fix README MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [ Co-authored-by: Ryan (hackercat) --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 22c3957..984c0c4 100644 --- a/README.md +++ b/README.md @@ -188,6 +188,16 @@ 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: