diff options
| author | techknowlogick <techknowlogick@gitea.io> | 2023-06-05 11:28:51 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-06-05 11:28:51 -0400 |
| commit | d302a5ee651e7dfebfc10980be9dea7cc7511373 (patch) | |
| tree | ff3ddb98045608662cc9659604dbe5236f0cfd0b | |
| parent | 395a6fabf356c258570a7d0cba0b6693984edac2 (diff) | |
| download | gitea-d302a5ee651e7dfebfc10980be9dea7cc7511373.tar.gz gitea-d302a5ee651e7dfebfc10980be9dea7cc7511373.zip | |
change placeholders in actions docs
| -rw-r--r-- | docs/content/doc/usage/actions/act-runner.en-us.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/content/doc/usage/actions/act-runner.en-us.md b/docs/content/doc/usage/actions/act-runner.en-us.md index 888b4cca36..b654fe2efa 100644 --- a/docs/content/doc/usage/actions/act-runner.en-us.md +++ b/docs/content/doc/usage/actions/act-runner.en-us.md @@ -177,7 +177,7 @@ To be clear, the "host" actually means the container which is running the act ru If you do not intend to use `actions/cache` in workflow, you can ignore this section. If you use `actions/cache` without any additional configuration, it will return the following error: -> Failed to restore: getCacheEntry failed: connect ETIMEDOUT <ip>:<port> +> Failed to restore: getCacheEntry failed: connect ETIMEDOUT IP:PORT The error occurs because the runner container and job container are on different networks, so the job container cannot access the runner container. |