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.

DNS unmarshal error when pulling from private repo with long url

See original GitHub issue

Actual Behavior

Recently updated to 1.1.1 hoping it’d resolve, but still having this same issue which I was also having with 1.1.0 and commented on thru issue 893

Pulling from public repos works fine, but when I try to pull from my team’s private repos over our company VPN and containing long urls, I get back cannot unmarshal DNS message below. This does not happen with Docker Desktop which uses kubernetes.docker.internal that’s mapped to my local (Windows) host in c/Windows/System32/drivers/etc/hosts.

docker pull teams-docker-dev-repo.docker.artifactory.my-company.com/base/service-img:10b2d1bb

Error response from daemon: Get "teams-docker-dev-repo.docker.artifactory.my-company.com/v2/": dial tcp: lookup teams-docker-dev-repo.docker.artifactory.my-company.com on 172.18.71.212:53: cannot unmarshal DNS message

Since my local Docker Desktop instance can pull the same private repo image down w/o issue while connected to the same VPN, I don’t think it has anything to do with the DNS issue in the Rancher Desktop context, but added that detail in case it does for any reason(s).

Steps to Reproduce

Try to pull an image from a long repo url, e.g. docker pull teams-docker-dev-repo.docker.artifactory.my-company.com/base/service-img:10b2d1bb. This same url works w/o issue on Docker Desktop, not sure what the deltas are and why it would be able to handle the same url w/o issue

Result

Error response from daemon: Get "teams-docker-dev-repo.docker.artifactory.my-company.com/v2/": dial tcp: lookup teams-docker-dev-repo.docker.artifactory.my-company.com on 172.18.71.212:53: cannot unmarshal DNS message

Expected Behavior

I should be able to pull from both public and private docker image repos with longer urls the same way I can in my Docker Desktop context

Additional Information

No response

Rancher Desktop Version

1.1.1

Rancher Desktop K8s Version

1.21.9

Which container runtime are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

10.0.18363 Build 18363

What CPU architecture are you using?

x64

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

No response

Windows User Only

Using Cisco AnyConnect VPN

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
AaronFrielcommented, Mar 15, 2022

@Nino-K I have good news, I’d root caused this and worked with the Go team to ensure this was released & backported: https://github.com/golang/go/issues/51127

1reaction
Nino-Kcommented, Mar 16, 2022

@kingrichard2005 I’m going to close this issue, however, feel to reopen at any time if this is not resolved by our next release. Thanks again for your contribution.

Read more comments on GitHub >

github_iconTop Results From Across the Web

net: 512 byte DNS response size limit causes "cannot ... - GitHub
So, you found this issue googling for "cannot unmarshal DNS" There's ... DNS unmarshal error when pulling from private repo with long url ......
Read more >
Private Repositories - Declarative GitOps CD for Kubernetes
Private repositories that require a username and password typically have a URL that start with https:// rather than git@ or ssh:// . Credentials...
Read more >
mongodb dump fails with cannot unmarshal DNS message
This is just a case of incompatible DNS server. Locate /etc/resolv.conf file and replace the nameserver with 8.8.8.8 , and everything should ...
Read more >
Docker Engine release notes
Error starting daemon: json: cannot unmarshal string into Go value of type types.PluginEnv. To manually remove all plugins and resolve this ...
Read more >
Common Error Messages - Troubleshoot | Consul
Troubleshoot issues based on the error message. Common errors result from failed actions, timeouts, multiple entries, bad and expired certificates, ...
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