-
Notifications
You must be signed in to change notification settings - Fork 836
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
Ubuntu 20.04 apt update - Temporary failure resolving #7737
Comments
From the output it looks like DNS is failing. Does putting this:
in /etc/resolv.conf help ? |
With
and
I'm not sure it is a dns problem. In the apt update with This morning I have
The opensuse has nerver worked but the the ubuntu ones it depends. Some are working but not always the same. I don't understand what's happening and how to 'debug' it. |
/dupe #8365 |
Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Version
Microsoft Windows [version 10.0.19044.1348]
WSL Version
Kernel Version
4.19.128
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
After installing the ubuntu distribution, I can do
sudo apt udate
and it gives me.I then added the podman repository in
/etc/apt/sources.list
:deb http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04/ /
Now the update gives me
Yet
If I try with opensuse ip, it's working
It seems that it is always working with that 'trick' except, time to time, the same error on one/multiple ubuntu repositories.
I'm working on a corporate laptop behind a proxy and using a vpn.
I never managed to have opensuse repository working with it's name yet a ping is working. For other coworkers, it's working.
So ... what could be the problem ?
I don't think it has something to do with network/proxy/internet...
But what ? Something with my laptop ? Something wrong with wsl2 ?
Expected Behavior
See above
Actual Behavior
See above
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: