Docker deamon only starts on login

[Dawnkeeper]

Expected behavior

Be able to get the demon running without logging into the machine

Actual behavior

Login required to start docker.

Information

• Windows Version: Win10 V 1607 (OS Build 14393.2363)
• Docker for Windows Version: 18.06.1-ce-win73 (19507)

Both services "DockerEngine" and "Docker for Windows service" are set to start automatically

[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

[Dawnkeeper]

/lifecycle frozen

[Dawnkeeper]

/remove-lifecycle stale

[Dawnkeeper]

Some more interaction than just a robot would be nice.

[sabujp]

This is a very annoying issue where we have to create our own task scheduler startup scripts or secondary services for something that should automatically be handled by Docker. Please fix this bug. FWIW I have a powershell script that does this on startup as a workaround:

$docker_wait = 25
function Restart-Docker {
  net stop docker
  net stop com.docker.service
  taskkill /IM 'dockerd.exe' /F
  taskkill /IM 'Docker for Windows.exe' /F
  net start docker
  net start com.docker.service
  Start-Process 'c:\program files\docker\docker\Docker for Windows.exe'
}

# Docker For Windows.exe might not be immediately ready
$sleep_multiplier = 0
do {
  Restart-Docker
  $sleep_seconds = $docker_wait * ++$sleep_multiplier
  Write-Output "Sleeping for $sleep_seconds seconds"
  Start-Sleep $sleep_seconds
  docker images
} while ($LASTEXITCODE -ne 0)

[sabujp]

how do we update the version label on this to the most recent stable one? This is actually a regression from 18.01 I think.

[pleonex]

This is making Docker really difficult to use in CI build servers. Every time the build server restarts some admin must login into it just to make Docker starts or make some custom scripts that must be maintained...

PS: one year and half without maintainers interaction. Good way to handle the community. Even if it's not in your priorities it would be great to say that and confirm this limitation.