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

"docker pull" fails in windows 10 #1928

Closed
1 task done
blacng opened this issue Apr 9, 2018 · 3 comments
Closed
1 task done

"docker pull" fails in windows 10 #1928

blacng opened this issue Apr 9, 2018 · 3 comments

Comments

@blacng
Copy link

blacng commented Apr 9, 2018

I followed the instructions here to run linux container on windows.

I entered this command in cmd (Ran as administrator):

C:\Users\USER\> set LCOW_SUPPORTED=1
C:\Users\USER> .\dockerd.exe -D --data-root C:\lcow

I also tried this command as suggested here:
C:\Users\USER> .\dockerd.exe -D --experimental --data-root C:\lcow

Then I entered this command in Windows Powershell (Ran as administrator):
C:\Users\USER> .\docker.exe pull ubuntu

I also see this error message in cmd:

ERRO: Resolver Setup/Start failed for container nat, "error in opening name server socket listen udp ... bind: Only one usage of each socket address (protocol/network address/port) is normally permitted."

  • I have tried with the latest version of my channel (Stable)
  • Windows Version: Windows 10
  • Docker for Windows Version: Version 18.03.0-ce-win59 (16762)

Expected behavior

  • Pulling from library ubuntu

Actual behavior

  • no matching manifest for windows/amd64 in the manifest list entries
@rn
Copy link
Contributor

rn commented Apr 10, 2018

With Docker for Windows you do not need to follow the instructions you reference (they are outdated in any case). If you switch, with the UI, to window containers you should see a pop up telling you how to use LCOW (there is no need to environment variables or starting the docker daemon manually).

then you can do:

docker pull --platform=linux ubuntu

Note, there is a PR for upstream moby/moby under review which will remove the need for the --platform=linux flag in the future.

I'm closing this issue. Let us know if you have additional quiestions/issues

@rn rn closed this as completed Apr 10, 2018
@blacng
Copy link
Author

blacng commented Apr 10, 2018

Thank you @rn.

@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 27, 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

3 participants