Usually, this error occurs after changing the hostname of your system. Attempt to use the sudo command after updating the hosts file and it should work fine.
#Sudo unable to resolve host windows 10 update#
To address this issue update the hostname or FQDN of the Archiving server in the /etc/hosts file and save the file. > else sudo sed -i "s/127.0.0.1 localhost/127.0.0. 9 I have installed Ubuntu 20.04 LTS on WSL. Sometimes we encounter an error sudo unable to resolve host. This issue can occur if the host name is not updated or incorrect in the /etc/hosts file. This is the result of using sudo fresh out of the box.īelow, the hostname is missing in /etc/hosts, which results in the error in the command that is made to fix it, which we can then see sudo no longer results in afterwards. Example: 127.0.0.1 hostname Attempt to use the sudo command after updating the hosts file and it should work fine.
#Sudo unable to resolve host windows 10 install#
The install is aware of the hostname, but in my case didn't get set in /etc/hosts for localhost, sudo calls made on the system result in hostname resolution errors. echo 127.0.0.1 computername > /etc/hosts That should fix the host name resolution One small request: If you liked this post, please share this One 'tiny' share from you would seriously help a lot with the growth of this blog. Solution: This issue can occur if the host name is not updated or incorrect in the /etc/hosts file. Its a great opportunity for developers across the globe to turn your ideas into reality. I didn't see it on the issues here in a search or perusing the pages, sorry if it's a duplicate. It should be possible to add an extra command post install if detected. I met the same issue with VPN, and in my case, the root cause is the DNS resolution, wsl will update the /etc/nf automatically based on the network which is nameserver 192.168.1. Fairly simple issue here, possibly an upstream bug due to the image used, as appears to be reported in a few different ubuntu images.
0 kommentar(er)
