[Question]: Self-hosted runner as a Service - The term 'docker' is not recognized

[JeppeBylov]

AL-Go version

7.1

Describe the issue

Hi,

I've succesfully configured multiple self-hosted runners on a local Hyper-V VM.
Today i wanted to set one of the self-hosted runners to run as a service, so i could skip having the powershell windows running.

However when the runner runs as a service it seems there are things it's not finding.

I get this error:
The term 'docker' is not recognized as the name of a cmdlet, function, script file, or operable program.

When i run the runner in a Powershell prompt, everything runs just fine.

Expected behavior

I was expecting it to run just as well as in a powershell prompt.

Steps to reproduce

• Set up a new self-hosted runner
• Set it to run as a Service, with NETWORK SERVICE account
• Try to run a CI/CD action

Additional context (logs, screenshots, etc.)

NETWORK SERVICE account is part of local administrators group.

[freddydk]

Use "NT AUTHORITY\SYSTEM" instead of NETWORK_SERVICE.

[JeppeBylov]

Doesn't seem to be enough.
I removed the runner and set it up fresh as a service using NT AUTHORITY\SYSTEM

Still getting the error..

[freddydk]

How did you install docker?
Are you using Docker Desktop - then that might be user specific.
I am using this script: https://github.com/microsoft/nav-arm-templates/blob/main/InstallOrUpdateDockerEngine.ps1 - with EnvScope set to Machine (instead of User)

[JeppeBylov]

I followed your guide from: https://github.com/microsoft/AL-Go/blob/main/Scenarios/SelfHostedGitHubRunner.md#create-your-self-hosted-runner-manually
Which uses the same script.

I'll try running it with envscope machine instead of User.

[JeppeBylov]

Reinstalled Docker with envScope machine did the trick.

[freddydk]

I have added this info to the above description - here 1acf2d9 - will be included when my updateDocs PR makes it in.