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

Unable to pull images with WSL2 engine #6494

Closed
2 tasks done
sefranz opened this issue Apr 29, 2020 · 3 comments
Closed
2 tasks done

Unable to pull images with WSL2 engine #6494

sefranz opened this issue Apr 29, 2020 · 3 comments

Comments

@sefranz
Copy link

sefranz commented Apr 29, 2020

I am not able to access the official docker registry in any way. This includes but not limited to:

  1. Registry login through docker login
  2. Pulling any images
  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: 4FABF347-80B2-4BEF-909D-538C79B1720F/20200429113855

Expected behavior

When starting the getting-started container the image is pulled and a corresponding container is started.

Actual behavior

 $ docker run -dp 80:80 docker/getting-started
Unable to find image 'docker/getting-started:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/docker/getting-started/manifests/latest: Get https://auth.docker.io/token?scope=repository%3Adocker%2Fgetting-started%3Apull&service=registry.docker.io: unexpected EOF.
See 'docker run --help'.

Information

  • Windows Version: Windows 10 Pro 2004 (Build 19041.208)
  • Docker Desktop Version: 2.3.0.1 (44875) [edge Channel]
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No
  • Further: I am using the WSL 2 based engine

Steps to reproduce the behavior

  1. Install docker desktop with WSL 2 based engine
  2. Run docker run -dp 80:80 docker/getting-started
@joshward
Copy link

I had this same issue. My problem was that I had the Docker CLI installed directly on WSL.

I switched docker for windows back to Hyper-V, then uninstalled the Docker CLI from WSL. After turning back on WSL integration everything worked.

@sefranz
Copy link
Author

sefranz commented May 15, 2020

This fixed my issue as well, I owe you many thanks

@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 Jul 15, 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