I am trying to understand, why I am unable to run
apt-get update from within my docker containers, either
- I am able to
ping 184.108.40.206or other address from within the container
- I am able to
ping google.comor other domains from within the container
apt-get updateworks if I start the container with
apt-get updatedoes not work if the container is connected to the default
bridgenetwork or any other user defined network with adapter set to bridge
- The host is a virtual machine managed by openstack
- Everything works as expected on my computer (not openstack, not virtual)
apt-get update will time out with:
root@66230c3e7572:/# apt update Err:1 http://deb.debian.org/debian buster InRelease Connection failed (IP: 220.127.116.11 80) Err:2 http://security.debian.org/debian-security buster/updates InRelease Connection failed (IP: 18.104.22.168 80) Err:3 http://deb.debian.org/debian buster-updates InRelease Connection failed (IP: 22.214.171.124 80) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Connection failed (IP: 126.96.36.199 80) W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease Connection failed (IP: 188.8.131.52 80) W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Connection failed (IP: 184.108.40.206 80) W: Some index files failed to download. They have been ignored, or old ones used instead.
I would like to find out why
apt-get udpate is not working while I’m connected to any
bridge network on the virtual machine. So any hints on how to debug this problem are very appreciated.