![]() ![]() TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 RX packets:7 errors:0 dropped:0 overruns:0 frame:0 They have been ignored, or old ones used instead.Ĭontainer IFCONFIG/PING ➜ code docker run -it ubuntu ifconfigĮth0 Link encap:Ethernet HWaddr 02:42:ac:11:00:04 Sending build context to Docker daemon 51.03 MBĬannot initiate the connection to :80 (2001:67c:1360:8c01::19). I'm out of ideas as to how to solve this problem, can anyone help?Įrror Message ➜ arthouse git:(docker) ✗ docker build -no-cache. I've thoroughly researched this through other posts on stackoverflow and github issues, but haven't found any resolution. I'm not behind a proxy, I'm on a very standard local network, and this version of Ubuntu is up to date and fresh (I installed two days ago to be closer to docker). It's weird because while DNS does not work, I still get a response when I ping the same update servers that apt-get can't resolve. I also tried pulling coreos, and yum could not resolve DNS either. I also set the DNS to Google in the DOCKER_OPTS of /etc/default/docker and restarted docker. I changed my /etc/nf nameservers from my local DNS server to Google's public DNS servers (8.8.8.8 and 8.8.4.4) and still have no luck. I disabled IPv6 on my host machine and still, removed all images, pulled base ubuntu, and still ran into the problem. The error output below initially lead me to believe it was because apt-get is trying to resolve the DNS via IPv6. I understand that there are different manual ways to fix this issue, but as in the first time it did work for me, and as I would assume that the stack creation process is automatic, I suspect that there is some config/cache/? issue I am not aware of.I'm running into a problem with my Docker containers on Ubuntu 14.04 LTS.ĭocker worked fine for two days, and then suddenly I lost all network connectivity inside my containers. I have gone through the steps three times already, but it always comes down to this.īased on that, I inserted the private ip/dns into etc/hosts, but it did not help (though it talks about 'network restart'. Since the second attempt, however, whenever I try to do anything there with sudo it reacts very slowly and I got the unable to resolve host ip-172-31-xx-xxx: Temporary failure in name resolution message. This is how I create the stack aws cloudformation create-stack \Īnd this is how I access it: ssh -i influxdb_example_3.pem manage to create the stack/instance and access it. GroupDescription: for the app nodes that allow ssh I had another issue with an instance, so I decided that I delete it and redo the steps to create a new one:Īpt-get install -y apt-transport-https ca-certificatesĪpt-key adv apt-key adv -keyserver hkp://:80 -recv-keys 58118E89F3A912897C070ADBF76221572C52609DĪpt-get update -qq apt-get purge lxc-docker || trueĪdd-apt-repository "deb bionic stable"Īpt-get -y install linux-image-extra-$(uname -r) linux-image-extra-virtualĭocker image pull quay.io/influxdb/influxdb:v2.0.2ĭocker container run -p 80:9999 quay.io/influxdb/influxdb:v2.0.2 ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |