<p>Restart docker, it falls into this state after the OS reboots. </p>

<p>The below thread mentions running it a swarm as preventing the issue from reoccurring and several ways to resolve the underlying OS issue with the software that may, or may not be workable for you. </p>

<p><a href="https://github.com/docker/for-win/issues/1038" rel="nofollow noreferrer">https://github.com/docker/for-win/issues/1038</a></p>

CC BY-SA 4.0
2019-01-08T03:18:18.073Z
2019-01-08T03:18:18.073Z
Absurdly
<p>I trying on Windows 10, Trying to connect / login to work interactively on container but I'm getting this kind of error </p>

<pre><code>docker run --rm -p 8080:80 laravel-docker
 Error response from daemon: driver failed programming external connectivity on endpoint wizardly_diffie (0c95bf862e583179e0a988eae0b07606e41184548c494ddd523df95c1430422f): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:8080:tcp:172.17.0.8:80: input/output error.
</code></pre>

<p>How to resolve this.</p>

<p>my docker version </p>

<pre><code>$ docker --version
Docker version 18.09.0, build 4d60db4
</code></pre>

<docker><php><docker-machine>
I trying on Windows 10, Trying to connect / login to work interactively on container but I'm getting this kind of error
Kishore
# I trying on Windows 10, Trying to connect / login to work interactively on container but I'm getting this kind of error

(Asked by: username_0 on 2019-01-07)

I trying on Windows 10, Trying to connect / login to work interactively on container but I'm getting this kind of error 
docker run --rm -p 8080:80 laravel-docker
 Error response from daemon: driver failed programming external connectivity on endpoint wizardly_diffie (0c95bf862e583179e0a988eae0b07606e41184548c494ddd523df95c1430422f): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:8080:tcp:172.17.0.8:80: input/output error.

How to resolve this.
my docker version 
$ docker --version
Docker version 18.09.0, build 4d60db4

**Tags:** docker, php, docker-machine


---

## 1 answers

### Answer by username_1 on 2019-01-08. Score: 1

Restart docker, it falls into this state after the OS reboots.

The below thread mentions running it a swarm as preventing the issue from reoccurring and several ways to resolve the underlying OS issue with the software that may, or may not be workable for you.

<https://github.com/docker/for-win/issues/1038>


---

