mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #1866] Cache server EHOSTUNREACH #908
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#908
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yknx4 on GitHub (Jun 15, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1866
Bug report info
Command used with act
Describe issue
Cache is not working on WSL2, it cannot reach the server and thus all cache actions always fail.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
This is running in Windows with WSL2
@wolfogre commented on GitHub (Jun 16, 2023):
In some environments, act cannot detect the correct IP to bind for the cache server (and artifact server).
"The correct IP" means it's accessible from Docker containers. I'm not familiar with WSL2, but I think you could try other IPs of your sub Linux system and specify it manually via
act --cache-server-addr <IP>.@yknx4 commented on GitHub (Jun 16, 2023):
@wolfogre Hey, I looked at it and it seems it is a little more complicated than that. It seems a docker container can't communicate with a WSL instance (The windows VM) it can only do it to the Windows host. so it can never reach the act process running locally. I'm looking for ways to fix this, either on the wsl side or maybe on the docker side. I'll let you know if I found something relevant to the project and probably add a PR to the Readme to make it run on WSL2 properly
@ChristopherHX commented on GitHub (Jun 16, 2023):
I had this problem over a year ago, (not with act, but similar kind of network issue)
I think in my case was docker.host.internal also broken at the same time.
Somewhat offtopic, windows container would need a windows firewall rule due to network adapter setup
The wsl problem seem to be different...
host.docker.internalhas a different ip inside wsl2@mikicho commented on GitHub (Sep 3, 2023):
@yknx4 I have the same problem. Did you find something?
@StefanLobbenmeierObjego commented on GitHub (Sep 29, 2023):
I also ran into this issue on macOS, but was able to solve this using
--cache-server-addr host.docker.internal
Might make sense to have that be the default on macOS?
@github-actions[bot] commented on GitHub (Mar 28, 2024):
Issue is stale and will be closed in 14 days unless there is new activity
@mikicho commented on GitHub (Mar 28, 2024):
don't
@mikicho commented on GitHub (Apr 10, 2024):
My solution was to stop using the docker desktop. I didn't use the GUI anyway..
@leotm commented on GitHub (Jul 25, 2024):
had similar issue on macOS
[CI/task] 💬 ::debug::getCacheEntry - Attempt 2 of 2 failed with error: connect ECONNREFUSED 172.16.0.2:55712☝️ works
@github-actions[bot] commented on GitHub (Jan 22, 2025):
Issue is stale and will be closed in 14 days unless there is new activity
@tjhiggins commented on GitHub (Jan 28, 2025):
Ran into this issue on WSL2. Fix was to not use the default docker network=host
.wslconfig
@lars18th commented on GitHub (Mar 5, 2025):
I recommend to put this on some document. It's necessary to overcome the timeouts using WSL2
@MuhammadSawalhy commented on GitHub (Apr 11, 2025):
I have hard time with this bug :(
Where should I put
.wslconfig?Edit: found the answer using the AI :)
It should be here
C:\Users\<YourUsername>\.wslconfig. Thanks for the solution <3@stickeegreg commented on GitHub (Aug 21, 2025):
Hopefully this will be fixed by #5912 (works with default WSL settings)