May-22nd-2019, 02:18 PM
Hello Andreas,
the point is as follows. The reason why you are getting access to portainer.io via "cifx0" but in the end this portainer.io not to DockerHub is the following:
If you remove the "eth0" or "wlan0" interface physically then the Host Linux will remove the DNS server from its local "/etc/resolve.conf" file.
If now portainer.io wants to request an image from "registry-1.docker.io" then the Host Linux cannot resolve this name and give you back an error like
And even if a container is started in Host and priviledge mode, it cannot access the file "/etc/resolve.conf" on the host, else you could easily insert a new DNS server entry like "nameserver 8.8.8.8" for example.
Armin
the point is as follows. The reason why you are getting access to portainer.io via "cifx0" but in the end this portainer.io not to DockerHub is the following:
If you remove the "eth0" or "wlan0" interface physically then the Host Linux will remove the DNS server from its local "/etc/resolve.conf" file.
If now portainer.io wants to request an image from "registry-1.docker.io" then the Host Linux cannot resolve this name and give you back an error like
Code:
Failure
Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: server misbehaving
And even if a container is started in Host and priviledge mode, it cannot access the file "/etc/resolve.conf" on the host, else you could easily insert a new DNS server entry like "nameserver 8.8.8.8" for example.
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)