Start Docker when log in, Timeouterror

[leejinseok]

Expected behavior

Successfully service start

Actual behavior

Sometimes docker start failed, with timeoutmessage,
then
I set DNS Server address fixed,
However, sometimes(not always sometimes done!) failed with timeout message

Information

[09:06:06.783][NamedPipeServer][Error  ] Unable to execute Mount: Docker command did not complete within the allowed timeout. Output:     위치: Docker.Backend.MobyCommand.RunDocker(String arguments, IDictionary`2 envVariables, String stdin, Int32 timeoutMs, String cidFile) 파일 C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\MobyCommand.cs:줄 152
   위치: Docker.Backend.MobyCommand.Run(String commandLine, IDictionary`2 envVariables, Boolean load, String stdin, Int32 timeoutMs) 파일 C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\MobyCommand.cs:줄 49
   위치: Docker.Backend.SambaShare.MountInMoby(String mount, String drive, Credential cred, CredentialInfo credInfo, String options, String ip) 파일 C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\SambaShare.cs:줄 197
   위치: Docker.Backend.SambaShare.MountInMoby(String drive, Credential credential, Settings settings) 파일 C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\SambaShare.cs:줄 168
   위치: Docker.Backend.SambaShare.Mount(String drive, Credential credential, Settings settings) 파일 C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\SambaShare.cs:줄 65
   위치: Docker.Backend.BackendServer.<Run>b__5_11(Object[] args) 파일 C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\BackendServer.cs:줄 54
   위치: Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) 파일 C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:줄 145

Of course, I succeed when I restart docker it again. But sometimes it's annoying that such things happen.

[Geekimo]

Hello,
I do have the same problem with the same output.
I've submitted the bug log several times.

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked