question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to build - Image Fetch Error - service/builder is not available/installed on Windows 10 & WSL2 for v1.0.0-beta-1 and v1.0.0

See original GitHub issue

Rancher Desktop Version

1.0.0-beta-1 and 1.0.0

Rancher Desktop K8s Version

1.23.1

What operating system are you using?

Windows

Operating System / Build Version

19043.1466

What CPU architecture are you using?

x64

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

No response

Windows User Only

VPN is ZScaler

Actual Behavior

After installing the above version, when I run a kubectl get all -A -o name command I do not see a listing for the builder service. Additionally I also cannot build any docker files. When I attempt to do so, I get the error ‘Unrecognized Image Format’. Additional text of the error is:

error: failed to solve: node:lts-alpine; failed to do request: Head "https://registry-1.docker.io/v2/library/node/manifests/lts-alpine": dial tcp: lookup registry-1.docker.io on .... : i/o timeout

Steps to Reproduce

Install beta version as above with ZScaler running and attempt to build any docker file.

Result

[+] Building 10.4s (3/3) FINISHED
=> [internal] load build definition from Dockerfile                                                               0.3s
=> => transferring dockerfile: 953B                                                                               0.1s
=> [internal] load .dockerignore                                                                                  0.3s
=> => transferring context: 2B                                                                                    0.1s
=> ERROR [internal] load metadata for docker.io/library/node:lts-alpine                                          10.0s
------
> [internal] load metadata for docker.io/library/node:lts-alpine:
------
Dockerfile:1
--------------------
   1 | >>> FROM node:lts-alpine
   2 |
   3 |     # Install chromium manually
--------------------
error: failed to solve: node:lts-alpine: failed to do request: Head "https://registry-1.docker.io/v2/library/node/manifests/lts-alpine": dial tcp: lookup registry-1.docker.io on 192.168.0.1:53: read udp 192.168.3.43:55223->192.168.0.1:53: i/o timeout
FATA[0011] unrecognized image format

Expected Behavior

Rancher Desktop should be able to build the docker file.

Additional Information

No response

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

3reactions
lincoln42commented, Jan 28, 2022

@gaderGarcia you are right, the issue is a DNS issue wherein when the rancher-desktop WSL distro starts up, it seems to put itself as the DNS server instead of properly picking up the DNS servers configured for the currently active (VPN or not) connection of the host. I came across this issue on the WSL board (https://github.com/microsoft/WSL/issues/5336) which again seems to be the same thing but people are running scripts to make the update manually.

I also came across this really good article (https://unix.stackexchange.com/questions/589683/wsl-dns-not-working-when-connected-to-vpn) on the issue and there ‘Rubin Simons’ has provided a PowerShell script that you can run via the task scheduler or just manually targeting your WSL distro to fix the DNS by picking up the connect DNS servers from the currently connected network adapter. I have tried this script and it works, I am able to build images now and the changes stick even after a reboot and going on and off the VPN as well.

@jandubois
Can the Rancher Desktop team take a look at making this DNS fix, provided by ‘Rubin Simons’, part of the product? It will save all of us having to make hacky script fixes for this issue. I have already burnt many productive hours finding a fix for this and it would save everyone else the hassle as well.

0reactions
Nino-Kcommented, Feb 18, 2022

We have implemented a process that defines the most suitable DNS servers in /etc/resolve.conf while on a dedicated VPN tunnel. These changes should be available in our next release. I’m going to close this issue, feel free to re-open if there is any feedback.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting Windows Subsystem for Linux | Microsoft Learn
Provides detailed information about common errors and issues people run into while running Linux on the Windows Subsystem for Linux.
Read more >
WSL2 Cannot connect to the Docker daemon - Stack Overflow
First, i have installed WSL v1 previously, then executed procedure for upgrade to WSL v2, and this error shows up: "ERROR: Cannot connect...
Read more >
Unable to build my docker image
I have a created a project as well as dockerfiles inside it. I'm trying to run it from docker but I keep getting...
Read more >
Linux on Windows with WSL2 – Part 4 - Devoteam
It is cool to play with some containers but let's see how our wsl2/ubuntu can help us to develop efficiently. Note 1. Docker...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found