Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot start container after Docker for Windows first launch #1752

Closed
sudoloic opened this issue Feb 26, 2018 · 6 comments
Closed

Cannot start container after Docker for Windows first launch #1752

sudoloic opened this issue Feb 26, 2018 · 6 comments

Comments

@sudoloic
Copy link

Expected behavior

Container should start with command docker start -i [container_name]

Actual behavior

Error when starting container with command docker start -i [container_name]:
Error response from daemon: driver failed programming external connectivity on endpoint [container_name](b67716c6c255663face61398ac447d72fe133ebb6402b5fd6a019a2d8fd6ae5c): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:8080:tcp:172.17.0.2:8080: input/output error

Docker for Windows needs to be relaunched to be able to start a container

Information

  • Diagnostic ID : 6CCDFB9C-855C-43BC-BDDC-CF2E9BCB90C2/2018-02-26_13-18-16
  • Always reproductible

Steps to reproduce the behavior

  1. Reboot computer
  2. Launch Docker for Windows
  3. Wait until Docker is started
  4. Run command docker start -i [container_name]
  5. Error : Error response from daemon: driver failed programming external connectivity on endpoint [container_name](b67716c6c255663face61398ac447d72fe133ebb6402b5fd6a019a2d8fd6ae5c): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:8080:tcp:172.17.0.2:8080: input/output error

Workaround

  1. Stop Docker for Windows
  2. Re-launch Docker for Windows
  3. Wait until Docker is started
  4. Run command docker start -i [container_name]
  5. Container started
@sudoloic
Copy link
Author

Well... duplicate of #1038

@firdanirp
Copy link

I solved this problem with restart my docker. I think this problem occured because we need to stop and exit docker before we shutdown our pc.

@docker-robott
Copy link
Collaborator

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

@jasonwilliams
Copy link

jasonwilliams commented Oct 9, 2018

/remove-lifecycle stale

This is still happening

Its always the first time.
After i restart docker it works

OS Name Microsoft Windows 10 Pro
Version 10.0.17134 Build 17134
Docker Version 2.0.0.0-beta1-win75 (19925)
Channel: edge
915f68b

Root Cause: #1967
Related: #1038
Related: #2722
Related: #573

@docker-robott
Copy link
Collaborator

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
Copy link
Collaborator

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

@docker docker locked and limited conversation to collaborators Jun 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants