Docker won't start containers after win 10 shutdown and power up. #1038

relnah · 2017-08-25T06:22:43Z

Expected behavior

After shuting down win 10 normally and with a working docker running, docker should be running as normal after powering up win 10.

Actual behavior

Starting containers fails with: Error response from daemon: Cannot restart container my_container: driver failed programming external connectivity on endpoint my_container (782f444833c57027050a58f8c0302473f76d9029a50944960d13c6ed940a4392): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:49161:tcp:172.17.0.2:1521: input/output error

docker compose up hangs.

Restart of docker engine will make it work again.

Information

Diagnostic ID 18D5608F-3086-460D-BD15-84F84F2C55D6/2017-08-25_08-09-32

Docker info:
Version 17.06.1-ce-win24 (13025)
Channel: stable
54dc09c

Win 10 info:
Edition: Windows 10 Enterprise x64
Version: 1703
OS Build: 15063.540
CPU: Inter Core i7-6600U 2.6GHz
RAM: 16 GB

Steps to reproduce the behavior

Start windows. Start docker and check "Start docker when you login".
Confirm docker is working as normal.
Do normal shutdown of windows.
Start up windows.
Confirm that docker has started.
Try starting a container. This fails with above mentioned problems.
Restart Docker. Starting containers work again.

RayDeCampo · 2017-08-30T20:10:21Z

I have the same issue although I have observed it happening when just logging out and logging back into my OS account. A restart of the docker service is the work-around. I am on Windows 10 Pro version 10.0.15063.502.

relnah · 2017-10-26T06:49:16Z

Still having this issue after latest docker and latest Win 10. Running linux containers to keep it consistent within our organization.
Disgnostic id: 18D5608F-3086-460D-BD15-84F84F2C55D6/2017-10-26_08-42-13
Docker version:
Version 17.09.0-ce-win33 (13620)
Channel: stable
8c56a3b

Win version:
Win 10 info:
Edition: Windows 10 Enterprise x64
Version: 1709
OS Build: 16299.19
CPU: Inter Core i7-6600U 2.6GHz
RAM: 16 GB

shillner · 2017-11-30T06:37:05Z

Hi, having the same issue on my machine. Settings are nearly identical to the ones of @relnah.
After shutdown or logout with running Docker for Windows the next docker startup is pretty fast but containers won't start. Only restarting docker helps at this point.

DirtyJerz · 2017-11-30T15:56:37Z

It seems the containers are still running ($docker ps) but the ports are no longer exposed (netstat -an). This is kinda frustrating and makes a multi-user or consecutive-session scenario inoperative.

relnah · 2018-01-09T07:57:46Z

Same issue after latest update:
Version 17.09.1-ce-win42 (14687)
Channel: stable
3176a6a

diag id:
18D5608F-3086-460D-BD15-84F84F2C55D6/2018-01-09_07-41-17

relnah · 2018-01-18T07:00:50Z

And still here:
Version 17.12.0-ce-win47 (15139)
Channel: stable
9c692cd

Error response from daemon: Cannot restart container xxxxx: driver failed programming external connectivity on endpoint xxxxx (bb96658514789875b9aabda58ee4312d26cabab216c516f34bcf34075b1db9a0): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:49161:tcp:172.17.0.2:1521: input/output error

Diag:
18D5608F-3086-460D-BD15-84F84F2C55D6/2018-01-18_07-58-02

kbeaskoetxea · 2018-01-24T08:14:19Z

Exactly the same issue here, I have to restart it whenever I shut down - power up my PC.

Docker info:
Version 17.12.0-ce-win47 (15139)
Channel: stable
9c692cd

Win 10 info:
Edition: Windows 10 Pro
Version: 1709
OS Build: 16299.192
CPU: Inter Core i5-7200U 2.5GHz
RAM: 12 GB

fiture · 2018-02-01T01:46:47Z

Same issue.

Error response from daemon: Cannot restart container xxx: driver failed programming external connectivity on endpoint lite (b7974e1da9cef2c73e75dcb7f6452cb753675e1c63feab82a4ccb433a5c337fe): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:8000:tcp:172.17.0.2:8000: input/output error

smiron · 2018-02-09T19:42:33Z

6 months later and I still have this issue. Hope they go bankrupt FFS

Update: 6 months later and I have 7 down emojis. Sooo scarry. Thanks guys. You made my day 🥇

jenspettersson · 2018-02-12T16:05:24Z

Same issue here. Shutting down Windows 10 with Docker For Windows running, but not set as "Start docker on login".

After restart I start Docker for Windows manually and my containers that should start automatically starts (a RabbitMQ container). However, it's not accessable and if I try to restart I get the same "driver failed programming..." error... I have to stop Docker for Windows and start it again.

dongshengYoung · 2018-02-13T01:50:31Z

when i sign out docker ,then sign in, the container can't

just quit docker and restart docker ,the container goes well.

my OS is win10

maybe restarting docke is a helpful way to solve problems of windows

Diedzz · 2018-02-16T12:07:33Z

same here, always have to restart docker after loging in to Win.

LeslieMurphy · 2018-02-16T21:55:12Z

Is this a Docker issue, or a Hyper-V issue? Not sure.

See https://forums.docker.com/t/overlay-network-broken-after-resuming-from-sleep/37376

jannikbuschke · 2018-02-22T05:58:58Z

same problem here

Christowiak · 2018-03-01T06:12:18Z

same problem here

fcavaco · 2018-03-01T10:29:18Z

same problem here

ramzgt · 2018-03-05T06:18:07Z

I have the same issue as well. Frustrating.

tkallevik · 2018-03-05T09:27:44Z

I also have the same problem.

Christowiak · 2018-03-05T17:10:31Z

i have found a solution on a other thread.

#573

The problem relies on the hybrid shutdown mode from the lastest win 10 updates. After disable it under energy options, the problem is solved for me.

kkajdd · 2018-03-08T08:45:06Z

restart of the docker after win10 boot up worked for me.

fiture · 2018-03-15T01:38:27Z

As @Christowiak say, Turn off fast startup works for me.
Uncheck Turn on fast startup and save. enjoy!
Control Panel > Hardware and Sound > Power Options > System Settings

quayal · 2018-03-21T07:46:41Z

I have the same issue, only that I can't see any containers; docker ps returns nothing

cchance27 · 2018-03-21T14:02:08Z

docker ps -a your containers are probably stopped still you''ll need to start them unless you set them to auto-restart

kbeaskoetxea · 2018-03-21T14:16:38Z

Yep. As @Christowiak said, I turn off Windows' fast startup and it goes fine.

relnah · 2018-03-21T14:38:59Z

Turning off OS features on my computer just to get Docker to work normally isn't really a soulution. A temporary workaround perhaps. So the issue is still valid.

ruifigueira · 2018-03-24T10:43:39Z

I couldn't find any UI to disable the hybrid shutdown mode as @Christowiak pointed out, so I went directly to regedit and created a Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableAutomaticRestartSignOn key (DWORD type) with value 1 and it seems to be working fine now.

More details on that property can be found in Winlogon Automatic Restart Sign-On (ARSO)
.

mfoulds · 2019-04-10T23:11:05Z

@NestorDR thanks for this. If we were to disable Docker's automatic startup on login in Docker Settings, then could we run your script instead, but without having to wait for Docker to stop?

Tiberriver256 · 2019-04-27T17:35:07Z

Easier methods for managing the "fast startup" mode via cmd.exe / PowerShell:

Turn on

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /V HiberbootEnabled /T REG_dWORD /D 0 /F

Turn off

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /V HiberbootEnabled /T REG_dWORD /D 1 /F

More Information / Other methods

https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

NestorDR · 2019-04-29T21:43:24Z

@mfoulds The problem arises because Docker does not stop formally at shutdown Windows, so the Docker must be started, in order to stop it formally.

StefanScherer · 2019-07-16T10:37:05Z

We're currently working on several issues and have a first edge preview to download which solves the problem with the "fast startup" mode in our test environment. It even restarts containers after a reboot and login that were started with the restart option eg. docker run -d -p 80:80 --restart always nginx.
I would love to hear your feedback if and how it helps in your environment.

mcopjan · 2019-07-16T15:31:30Z

@StefanScherer Unfortunately unable to install on Microsoft Windows Server 2016 Standard (10.0.14393 Build 14393), it says" Docker Desktop requires Windows 10 Pro or Enterprise version 15063 to run." :/
Currently using 2.0.0.3 (31259)

nrjohnstone · 2019-07-17T19:16:38Z

Downloading and trialing right now...

nrjohnstone · 2019-07-18T06:05:56Z

and after leaving some docker containers running, shutting down pc for 6 hours then restarting I get a crash from docker on starting (replicated multiple times)

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/containers/json: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

at Docker.Backend.DockerDaemonChecker.Check(Func`1 isDaemonProcessStillRunning)
at Docker.Backend.BackendNamedPipeServer.b__8_4(Object[] args)
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b__0(Object[] parameters)
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Lucky at this point of using docker on windows for the last 3 years I've become apathetic to announcments and new versions of docker solving anything.

mikeparker · 2019-07-18T10:50:06Z

@mcopjan Docker Desktop is for developer machines, not Windows Server. For Windows Server please see Docker Enterprise for Windows Server -> https://docs.docker.com/install/windows/docker-ee/

@nrjohnstone can you confirm Docker Desktop is set to startup on boot and not disabled in the windows startup tasks. Can you then check the status of your whale icon in your systray (if its broken, it will be red. If its not started at all it won't be there.) Assuming all this is fine can you then upload your log file or a diagnostic? The error message you posted just says docker isn't running, so diagnosing that will need more info. Thanks!

mcopjan · 2019-07-18T13:58:21Z

@mikeparker thanks, I installed docker EE on WS 2016, problem is I cannot switch into linux containers (I assume it is not supported?) So I am still stuck with Docker for Windows experiencing the reported issue.

nrjohnstone · 2019-07-20T07:16:13Z

@mikeparker I can confirm the following
After the install everything works and there is a Hyper-V machine "DockerDesktop" running.
After a reboot, the Hyper-V machine is still there, and running, but Docker Desktop starts, the whale icon in the system tray does it's thing for about 2-3 minutes then I get the error with the docker daemon not running.

I have to uninstall and revert back to the build from last year that I've been running as I don't really have the time to be a beta tester for this scenario.

I have uploaded the error log though.

I guess it's back to force killing docker to restart on every windows login again.

graham73may · 2019-07-20T07:23:23Z

@nrjohnstone
I have this exact issue and was really hoping you were going to come back with some good news!

I don't know if you will find either of these less painful than force killing docker:

Quit docker before shutting down.
Or
When you boot up... let the whale do it's thing. When it thinks it's ready, right click and hit restart docker.

The other annoying thing I've not managed to find a work around for is if I'm using docker and shut my laptop... Then open my laptop a bit later, the whole machine has effectively crashed and windows starts up from scratch instead of waking from sleep. (this only happens if docker is running, fine if it's not).

luisbodra · 2019-07-20T16:49:33Z

Hi, I am a user of Brazil and have experienced an error in my attempts to install [nwabap751] from the command line of my Linux container Ubuntu into Docker. The message appears on my screen:

PS C:\INST> docker run -p 8000:8000 -p 44300:44300 -p 3300:3300 -p 3200:3200 -h vhcalnplci --name nwabap751 -it nwabap751 /bin/bash
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: driver failed programming external connectivity on endpoint nwabap751 (89538c9c2ae1ab2541f308b6bd64cbff4024dc4ad773aa2096026a9a28bc76f4): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:44300:tcp:172.17.0.2:44300: input/output error.
PS C:\INST>

How can I solve this problem? Why it happens? Can you help me? Thanks for your help.

wasmup · 2019-07-31T19:03:07Z

Error:

docker:
Error response from daemon: driver failed programming external connectivity on endpoint pg1 (ee2507e963bb1effee71270ed0151d7e1c92cbb32615e0b176f4852892c4c596):
Error starting userland proxy: mkdir /port/tcp:0.0.0.0:5432:tcp:172.17.0.2:5432: input/output error.

For me: Solved by just Docker Restart (not OS).

docker version

Client: Docker Engine - Community
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        6247962
 Built:             Sun Feb 10 04:12:31 2019
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 04:13:06 2019
  OS/Arch:          linux/amd64
  Experimental:     false

ghost · 2019-08-02T07:48:12Z

i have found a solution on a other thread.

#573

The problem relies on the hybrid shutdown mode from the lastest win 10 updates. After disable it under energy options, the problem is solved for me.

This one worked for me.

relnah · 2019-08-16T06:18:13Z

After upgrade to latest stable Docker (2.1.0.1) my case now works without any workarounds, like disabling OS features.

I select to have Docker start on start up, I create a container with --restart unless-stopped.
Confirm that container is accessible and running ok.
Shut down windows.
Start windows.
Wait for Docker to automatically start.
Confirm that container is running ok and is accessible.

I'm running linux containers.

Version info:
{
"id": "",
"date": "2019-08-16 06:11:41.1555453 +0000 UTC",
"os": "Windows 10 Enterprise 10.0.18362",
"os_label": "win/18362",
"app_version": "2.1.0.1",
"app_channel": "stable",
"engine_version": "19.03.1",
"compose_version": "1.24.1",
"kubernetes_version": "v1.14.3",
"credhelper_version": "0.6.3",
"notary_version": "0.6.1",
"vpnkit_version": "218f01482560cba2fa863f9ad872ad51d1e717fc"
}

Thanks for the fix ;)

leftnet · 2019-08-16T10:42:57Z

This also seems to be working for me without workarounds in 2.1.0.1 now. Good job! 👍

Vespira · 2019-08-28T15:34:51Z

Restart didn't worked for me (tried multiple way to restart Docker), neither did disabling the "Experimental features" (as it were already disabled, anyway). We tried so much things, but we ended up doing a "Reset to factory" from Docker Desktop GUI, and magically, it worked again.

But man, I hate it when docker network or something have a corrupted state, it happens way too often. Plus, the issue that I have to effectivly restart Docker at each Windows start, but here, changing the shutdown strategy, like other users suggested, to "not fast startup" did the trick.

relnah · 2019-08-29T09:22:40Z

2.1.0.1 fixed it. Has been working well for a couple of weeks.

Vespira · 2019-08-29T09:36:48Z

I'm was already in version 2.1.0.1 (build 37199) when I had the issue I described earlier. So it has to be something else. I'll create an issue if I have the problem again anyway.

nfourniol · 2019-09-03T09:21:06Z

Still the same issue on 2.1.0.1 (build 37199)

Viir · 2019-09-16T09:52:56Z

docker run fails on Windows 10:

Error response from daemon: driver failed programming external connectivity on endpoint drtsgame-test-container (7597b6ceadc7356f20b918b1c46c648f1cabf99df3f82ef79093cf337d5ac9cb): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:443:tcp:172.17.0.2:443: input/output error.

docker version:

Client: Docker Engine - Community
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        6247962
 Built:             Sun Feb 10 04:12:31 2019
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 04:13:06 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Note about Docker version: The docker installer keeps hanging, see #1172 (comment)

Trying to restart docker:

After this restart, docker run worked, so this resolved the problem.

Illutax · 2019-11-11T13:12:59Z

Had an similar error. Restarting the system fixed it for me.

Apparently the system tried at some point an shutdown but it was interrupted. While trying to shutdown the OS stopped some services or driver required for docker.

andrebacaglini · 2019-12-04T12:05:03Z

As @Christowiak say, Turn off fast startup works for me.
Uncheck Turn on fast startup and save. enjoy!
Control Panel > Hardware and Sound > Power Options > System Settings

Disabling fast startup worked for me!

docker-robott · 2020-06-23T03:14:06Z

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

s-jeyaram mentioned this issue Aug 26, 2017

Docker V17.03.1-ce-win5(10743) doesn't start after installation on Windows 10 VM #613

Closed

sudoloic mentioned this issue Feb 26, 2018

Cannot start container after Docker for Windows first launch #1752

Closed

GzuPark mentioned this issue Mar 19, 2018

한글 자연어 텍스트 분석을 위한 환경 구성, 참고 자료 GzuPark/naver-ai-hackathon-2018#1

Closed

no1xsyzy mentioned this issue Mar 24, 2018

--restart always not work ziahamza/webui-aria2#447

Closed

cdrini mentioned this issue May 13, 2019

docker-compose up: driver failed programming external connectivity internetarchive/openlibrary#2121

Closed

relnah closed this as completed Aug 29, 2019

Vespira mentioned this issue Sep 3, 2019

Corrupted state after Windows shutdown #4637

Closed

2 tasks

Viir mentioned this issue Sep 16, 2019

docker run fails - "Error starting userland proxy: mkdir /port/tcp:0.0.0.0:443:tcp:172.17.0.2:443: input/output error." Viir/Kalmit#13

Closed

docker locked and limited conversation to collaborators Jun 23, 2020

docker-robott added the lifecycle/locked label Jun 23, 2020

Docker won't start containers after win 10 shutdown and power up. #1038

Docker won't start containers after win 10 shutdown and power up. #1038

Comments

relnah commented Aug 25, 2017 • edited Loading

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

RayDeCampo commented Aug 30, 2017

relnah commented Oct 26, 2017 • edited Loading

shillner commented Nov 30, 2017

DirtyJerz commented Nov 30, 2017

relnah commented Jan 9, 2018

relnah commented Jan 18, 2018

kbeaskoetxea commented Jan 24, 2018

fiture commented Feb 1, 2018

smiron commented Feb 9, 2018 • edited Loading

jenspettersson commented Feb 12, 2018

dongshengYoung commented Feb 13, 2018

Diedzz commented Feb 16, 2018

LeslieMurphy commented Feb 16, 2018

jannikbuschke commented Feb 22, 2018

Christowiak commented Mar 1, 2018

fcavaco commented Mar 1, 2018

ramzgt commented Mar 5, 2018

tkallevik commented Mar 5, 2018

Christowiak commented Mar 5, 2018 • edited Loading

kkajdd commented Mar 8, 2018 • edited Loading

fiture commented Mar 15, 2018 • edited Loading

quayal commented Mar 21, 2018

cchance27 commented Mar 21, 2018

kbeaskoetxea commented Mar 21, 2018

relnah commented Mar 21, 2018

ruifigueira commented Mar 24, 2018

mfoulds commented Apr 10, 2019

Tiberriver256 commented Apr 27, 2019

Turn on

Turn off

More Information / Other methods

NestorDR commented Apr 29, 2019

StefanScherer commented Jul 16, 2019

mcopjan commented Jul 16, 2019 • edited Loading

nrjohnstone commented Jul 17, 2019 • edited Loading

nrjohnstone commented Jul 18, 2019

mikeparker commented Jul 18, 2019

mcopjan commented Jul 18, 2019

nrjohnstone commented Jul 20, 2019 • edited Loading

graham73may commented Jul 20, 2019

luisbodra commented Jul 20, 2019

Hi, I am a user of Brazil and have experienced an error in my attempts to install [nwabap751] from the command line of my Linux container Ubuntu into Docker. The message appears on my screen:

wasmup commented Jul 31, 2019 • edited Loading

ghost commented Aug 2, 2019

relnah commented Aug 16, 2019 • edited Loading

leftnet commented Aug 16, 2019

Vespira commented Aug 28, 2019

relnah commented Aug 29, 2019

Vespira commented Aug 29, 2019

nfourniol commented Sep 3, 2019

Viir commented Sep 16, 2019 • edited Loading

Illutax commented Nov 11, 2019

andrebacaglini commented Dec 4, 2019

docker-robott commented Jun 23, 2020

relnah commented Aug 25, 2017 •

edited

Loading

relnah commented Oct 26, 2017 •

edited

Loading

smiron commented Feb 9, 2018 •

edited

Loading

Christowiak commented Mar 5, 2018 •

edited

Loading

kkajdd commented Mar 8, 2018 •

edited

Loading

fiture commented Mar 15, 2018 •

edited

Loading

mcopjan commented Jul 16, 2019 •

edited

Loading

nrjohnstone commented Jul 17, 2019 •

edited

Loading

nrjohnstone commented Jul 20, 2019 •

edited

Loading

wasmup commented Jul 31, 2019 •

edited

Loading

relnah commented Aug 16, 2019 •

edited

Loading

Viir commented Sep 16, 2019 •

edited

Loading