Support Windows
Michael-Tang-2009 opened this issue · 7 comments
Act version
V0.2.42
Feature description
I'm working with .NET Framework, but this act may not support it. So, I hope that this will be support Windows soon.
This feature is included in recent releases of nektos/act.
Warning add defaults.run.shell to your job, otherwise act tries to use bash instead of powershell.
./act -P windows-latest=-self-hosted -W test.yml
First of all. I want to thank you for your helping. I may not find docs about it right now, really. Hummmmm, there is some problem with it, just like the picture
.
I have two question here:
Does it runs on something like docker image?
I used the command that you posted out in the last commented, but there meight something goes wrong. Or maybe I need to download all the action code which I reference in my workflow file and put it into folder "action" or something else?
Does it runs on something like docker image?
No, it runs actions directly on your windows system.
I used the command that you posted out in the last commented, but there meight something goes wrong
You have to install nodejs from https://nodejs.org/en/ for most actions to work.
Otherwise you can only use composite actions and run scripts.
Thanks for all the helpings, I will try it later to make sure that runs correctly and I'll close this.
I want to advice that I meight cannot find anything about windows platform, so that I think it is important to add into README.md.
Hummmmm, I do not know how to deal with this:
time="2023-02-05T21:01:20+08:00" level=warning msg="unable to get git repo: remote not found"
time="2023-02-05T21:01:20+08:00" level=error msg="failed to obtain container engine info: error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/info": open //./pipe/docker_engine: The system cannot find the file specified."
I'm just ignoring that "failed to obtain container engine info"
error.
This windows mode has known issues, which might be good to resolve before documenting it for everyone.
- the docker connect error you posted
- the env context needs to be case insensitive on windows, but isn't right now.
- default shell on windows is wrong
- cmd cannot be used as shell
- ...probably more known issues
I'm also have the problem message like time="2023-02-06T09:08:36+08:00" level=warning msg="unable to get git repo: remote not found"
But I already checked the config file where under .git folder.