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 pull image #8088

Open
qzwzqty opened this issue Jan 15, 2025 · 2 comments
Open

cannot pull image #8088

qzwzqty opened this issue Jan 15, 2025 · 2 comments
Labels
kind/bug Something isn't working

Comments

@qzwzqty
Copy link

qzwzqty commented Jan 15, 2025

Actual Behavior

The following error occurs when pulling an image
Error response from daemon: failed to resolve reference "docker.io/timescale/timescaledb-ha:pg15": failed to do request: Head "https://registry-1.docker.io/v2/timescale/timescaledb-ha/manifests/pg15": EOF。
But with docker desktop don't have this problem

Steps to Reproduce

  1. install rancher-desktop 1.17.0
  2. open, configure (kubernetes disabled, container engine: dockered)
  3. rancher-desktop starts, default images visible in the images tab
  4. open CMD
  5. command : docker pull timescale/timescaledb-ha:pg15

Result

image

Expected Behavior

Expected result: docker image for timescale/timescaledb-ha:pg15 is pulled

Additional Information

No response

Rancher Desktop Version

1.17.0

Rancher Desktop K8s Version

1.28.5

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 11 Professional Edition 24H2

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

VPN clash

@qzwzqty qzwzqty added the kind/bug Something isn't working label Jan 15, 2025
@AdrianMetzner
Copy link

I was having the same issue. The problem seems to be the dns resolution. In the docker engine a non functional local dns was used. I could employ a workaround by setting the nameserver to a publically known one (1.1.1.1, 8.8.8.8) in the provisioning of rancher desktop.

@Nino-K
Copy link
Member

Nino-K commented Jan 15, 2025

Hi, what you are seeing is most likely related to the DNS resolutions not functioning correctly behind the VPN in v1.17.0, please see my comment here: #8055 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants