Open yknx4 opened 1 year ago
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>
.
@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
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.internal
has a different ip inside wsl2
@yknx4 I have the same problem. Did you find something?
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?
Issue is stale and will be closed in 14 days unless there is new activity
don't
My solution was to stop using the docker desktop. I didn't use the GUI anyway..
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