I definitely feels it’s related to Docker. This is the error info from Docker during the failed autostart.
Unable to start: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 'MobyLinuxVM' failed to start.
Failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running.
'MobyLinuxVM' failed to start. (Virtual machine ID 2F9D96CC-BB80-4942-95BA-07D6CC517247)
The Virtual Machine Management Service failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running (Virtual machine ID 2F9D96CC-BB80-4942-95BA-07D6CC517247).
at Start-MobyLinuxVM, <No file>: line 296
at <ScriptBlock>, <No file>: line 412
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object parameters) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 92
at Docker.Actions.<>c__DisplayClass19_0.<Start>b__0() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 74
at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59
Since the domain OU may be an issue, I moved the computer to a less restrictive OU. I’ve also researched the web with some of the keywords from the Docker error info and can’t seem to get a good fix in place.
As for the SQL password, I added one.
For getting Docker to start, I can still do the right-click taskbar icon and choose Restart and it does.
I attempted to run docker-compose up -d again and it still kicks back
ERROR: Windows named pipe error: The system cannot find the file specified. (code: 2)
I decided to run docker-machine ls to see what VMs exist and none show up. I’m not sure if that’s related. Maybe nothing is supposed to show up until I can successfully run docker-compose up -d.
Any other ideas about this Docker issue?