I've seen this issue with a couple of people in the past two weeks, and one of my build agents (that worked before) finally ran into the same issue.
During ALOpsCreateDocker, with perfectly normal settings:
- task: ALOpsDockerCreate@1
displayName: 'ALOPS - Create Docker Image' # It will reuse the image if already exists, or build one if it doesn't.
inputs:
artifacttype: Sandbox
memory: '8G'
I was getting the error Exception calling "Start" with "0" argument(s): "The system cannot find the file specified"
I was baffled, as I had the build agent service responding, it had rights to the OS/Docker, Docker was alive and working.
Turned out, when Docker installed last, it put the docker into my PATH for only my user not the machine. The trick was to go to System, Advanced System Settings, Environment Variables - and move the docker path to the System Variables version of the PATH.
Figured I'd add this issue here, as no search yielded this info/hint/thing to try, so now someone later will have a chance.
I've seen this issue with a couple of people in the past two weeks, and one of my build agents (that worked before) finally ran into the same issue.
During ALOpsCreateDocker, with perfectly normal settings:
I was getting the error
Exception calling "Start" with "0" argument(s): "The system cannot find the file specified"I was baffled, as I had the build agent service responding, it had rights to the OS/Docker, Docker was alive and working.
Turned out, when Docker installed last, it put the docker into my PATH for only my user not the machine. The trick was to go to System, Advanced System Settings, Environment Variables - and move the docker path to the System Variables version of the PATH.
Figured I'd add this issue here, as no search yielded this info/hint/thing to try, so now someone later will have a chance.