- Background
- As an endless life, tossing more than the yards of farmers. A variety of operating systems I do not know how many times, countless nights repair data overnight, re-install the system, that tired ah!!
- Option 1: Backup. The data can be backed up, the configuration can be backed up, and the installation package can be backed up. But the installation process is not good, poor cock after all kinds of installation to crack re-configuration, re-test, injury can not afford.
- Option 2: Complete system backup. Endless, backup can't afford ~ ~
- Option 3: Big kill Docker. Just a bunch of synology NAS can be deployed Docker, all the toss in the new container implementation, want to solidify the direct entire container backup, volume than system backup much smaller, easy to deploy, access good management.
- Problem
- Some of these docker is the secondary stability system, mainly Ubuntu, Kali, Metasploit, and so on, some of the development workers Zhe for Teng, or do not do the root of the good. New work account to play.
- But the internet is not good, crawl a data, sync a github can't play Ah, good trouble ~ ~
-
- Trace
- This ~ ~ is known as root can access the external network, the gateway, firewall and so on no problem, the system level should also not have problems.
- That's usually the problem with work account permissions. is the network card device access rights/network card IO Access/account configuration permissions? It's a little annoying to check.
- Then I ping the next 180.76.76.76 (Baidu Public DNS, can not ping baidu.com when ping this, haha)
- Good luck, can ping through.
- Self-study observation above error, found no!! Unknown host!!! The basic certainty is that the DNS problem is correct.
- Combined with root phenomenon, DNS configuration problem/dns configuration permissions Problem/dns profile access problem? This narrows it down a lot, and it's good to check.
- Look at the permissions and content of the/etc/resolv.conf
- This is obviously a problem, chmod 644/etc/resolv.conf get rid of. Under test.
- bingo!!
- Solve
- Chmod 644/etc/resolv.conf
Network access issues for Ubuntu new users on Docker
