starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00

[GH-ISSUE #5870] Add support for Docker Engine installed in WSL2 in GitHub Local Actions #1271

New issue

Open

opened 2026-03-01 21:50:04 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 21:50:04 +03:00

Owner

Originally created by @albal on GitHub (Jul 9, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/5870

Act version

act version 0.2.79

Feature description

There is an option to point to the Docker Desktop in the GitHub Local Actions settings. On Linux I have installed Docker Engine (not Docker Desktop - this means I am using Docker in my machine under the Apache License).

I would like to use Docker Engine in WSL2 under Windows 11. There is a warning when installing Docker Engine from https://get.docker.io/ but it is fine to run Docker in WSL2 on Windows 11 in this manner. You can provide a path reference to the Docker binary from Windows to WSL2 using UNC path:

\\wsl.localhost\Ubuntu\usr\bin\docker

It would be great to be able to support this option.

Originally created by @albal on GitHub (Jul 9, 2025). Original GitHub issue: https://github.com/nektos/act/issues/5870 ### Act version act version 0.2.79 ### Feature description There is an option to point to the Docker Desktop in the GitHub Local Actions settings. On Linux I have installed Docker Engine (not Docker Desktop - this means I am using Docker in my machine under the Apache License). I would like to use Docker Engine in WSL2 under Windows 11. There is a warning when installing Docker Engine from `https://get.docker.io/` but it is fine to run Docker in WSL2 on Windows 11 in this manner. You can provide a path reference to the Docker binary from Windows to WSL2 using UNC path: ```text \\wsl.localhost\Ubuntu\usr\bin\docker ``` It would be great to be able to support this option.

kerem added the

kind/feature-request

label

2026-03-01 21:50:04 +03:00

kerem commented

2026-03-01 21:50:04 +03:00

Author

Owner

@albal commented on GitHub (Jul 9, 2025):

I have found if you install and run VS Code from the WSL2 environment then the Docker Engine is detected.

@albal commented on GitHub (Jul 9, 2025): I have found if you install and run VS Code from the WSL2 environment then the Docker Engine is detected.

kerem commented

2026-03-01 21:50:04 +03:00

Author

Owner

@ChristopherHX commented on GitHub (Jul 9, 2025):

act does not use the cli tool of docker.

Yes if you run act inside the wsl2 where the docker.sock unix socket can be found act knows how to use it.

@ChristopherHX commented on GitHub (Jul 9, 2025): act **does not** use the cli tool of docker. Yes if you run act inside the wsl2 where the docker.sock unix socket can be found act knows how to use it.

kerem commented

2026-03-01 21:50:05 +03:00

Author

Owner

@darrylsepeda commented on GitHub (Oct 2, 2025):

act uses docker engine, while my docker engine is in WSL.

I tried to point docker engine to the one inside wsl, yet it is not working:

act --container-daemon-socket "\\wsl.localhost\Ubuntu\var\run\docker.sock"

"Couldn't get a valid docker connection: DOCKER_HOST was not set, couldn't be found in the usual locations, and the container daemon socket ('\\\\wsl.localhost\\Ubuntu\\var\\run\\docker.sock) is invalid"

how do you run VSCode from WSL?
I installed VSCode inside WSL, but received this error when I ran it:

To use Visual Studio Code with the Windows Subsystem for Linux, please install Visual Studio Code in Windows and uninstall the Linux version in WSL. You can then use the `code` command in a WSL terminal just as you would in a normal command prompt.
Do you want to continue anyway? [y/N] y
To no longer see this prompt, start Visual Studio Code with the environment variable DONT_PROMPT_WSL_INSTALL defined.
You are trying to start Visual Studio Code as a super user which isn't recommended. If this was intended, please add the argument `--no-sandbox` and specify an alternate user data directory using the `--user-data-dir` argument.

I agree with this issue ticket for act/github local action to support docker engine in WSL

@darrylsepeda commented on GitHub (Oct 2, 2025): act uses docker engine, while my docker engine is in WSL. I tried to point docker engine to the one inside wsl, yet it is not working: ``` act --container-daemon-socket "\\wsl.localhost\Ubuntu\var\run\docker.sock" "Couldn't get a valid docker connection: DOCKER_HOST was not set, couldn't be found in the usual locations, and the container daemon socket ('\\\\wsl.localhost\\Ubuntu\\var\\run\\docker.sock) is invalid" ``` how do you run VSCode from WSL? I installed VSCode inside WSL, but received this error when I ran it: ``` To use Visual Studio Code with the Windows Subsystem for Linux, please install Visual Studio Code in Windows and uninstall the Linux version in WSL. You can then use the `code` command in a WSL terminal just as you would in a normal command prompt. Do you want to continue anyway? [y/N] y To no longer see this prompt, start Visual Studio Code with the environment variable DONT_PROMPT_WSL_INSTALL defined. You are trying to start Visual Studio Code as a super user which isn't recommended. If this was intended, please add the argument `--no-sandbox` and specify an alternate user data directory using the `--user-data-dir` argument. ``` I agree with this issue ticket for act/github local action to support docker engine in WSL

kerem commented

2026-03-01 21:50:05 +03:00

Author

Owner

@panekj commented on GitHub (Oct 2, 2025):

https://nektosact.com/usage/custom_engine.html

@panekj commented on GitHub (Oct 2, 2025): https://nektosact.com/usage/custom_engine.html

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1271

No description provided.

Rows
Columns