![]() ![]() 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. Last edited by ClientAlive June 1st, 2011 at 08:19 PM.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. If one part gets thrown out of balance the rest of it messes up too. Or, to use our solar system as an example - each part works together to form the whole. I gather that most things are connected to one another in some way. It's just that these two things seem like they would be connected to one another - not separate. Not sure if I'm thinking about these things right or not though. The other is that the keyring be separated from the right password - except that I checked out what the password is set to in the keyring and it is the new one. One is that when I edit the hostname in those files things become separated between the hostname and the keyring. I mean, I can imagine two ways that things could go wrong on me. I'll google it right now though.Įdit: The keyring thing is kind of concerning to me also. Is there anything I can to to cover myself if some mistake were to be made and I got locked out of my computer or something? Is there some file or something I can save to my thumb drive or some way I could roll things back in case something goes wrong?Īlso I have never used recovery mode with Linux, nor have I ever read anything about how to do it or how it works. I'm having a hard time recalling which method I used to change the host name but I'm relatively certain I did that through the command line. That's the only way I know how to do that. I changed the password via the gui (system > administration > users and groups > ). ![]() Note: sudo works fine, it just complains, so you can edit it with the machine running instead of having to boot into recovery mode. Did you change your user account password from the commandline or via GUI?Īs for the "unable to resolve host" thing, it happens when you change hostnames.Įdit the /etc/hosts file and replace the old name with the new name. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |