sudo apt-get update in the new Windows Subsystem for Linux, but I get the following error:
The most relevant parts seem to be the "could not resolve" lines about Ubuntu servers, like:
Could not resolve 'archive.ubuntu.com'
There is an open GitHub issue about this error.
It appears that the most likely problem is that
/etc/resolv.conf didn't get generated correctly. Make sure it contains a
nameserver line for a valid DNS server, preferably one on your local network. Many routers provide DNS services to their networks; on my network, I would add this line:
If there are entries that don't correspond to valid DNS servers, remove them.
If you use a third-party antivirus product, try disabling its firewall - there are reports that some such programs interfere with Bash's connectivity.
/etc/apt/apt.conf to add proxy configuration.
sudo nano /etc/apt/apt.conf
Add this line to your
Save it with Ctrl+X, Y and retry:
Now run the below command
sudo apt-get update
I tried and verified.
It looks like your DNS settings are incorrect or you could have a gateway/netmask incompatibility.
ip link to verify that an interface is listed as 'up' and then
ifconfig to for the settings of that interface. you may also need to
cat /etc/sysconfig/network-scripts/ifcfg-eth? to look at the settings of the interfaces.
traceroute -d 188.8.131.52 to see if you can reach google's public DNS server. That will verify you are getting out to the outside network.
If it works with
-d but fails to resolve the IP's to names when run without the
-d then a quick fix would be to add 184.108.40.206 & 220.127.116.11 to your DNS Settings for the interface that is up, and then issue a
service network restart to restart the network services and make the DNS changes active.
I forgot if you don't have a gui interface configured yet, you can easily edit the interface configs with
system-config-network. Navigate with arrow keys,tab, esc, and enter
In my case this was actually caused by Norton "Smart" Firewall (ironic name). Disabling firewall brought the internet to life without editing any system files (WSL 2, Ubuntu 18.04). However setting nameserver to 18.104.22.168 fixed other issues
Works for CentOS/RHEL/Fedora:
Please set the proxy using the following command:
Command to set the proxy:
Command to verify whether proxy is set or not: