-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't pull image on my ubuntu 13.04 #1470
Comments
Maybe you have ufw enabled ? |
@vieux
|
If you launch the daemon in debug mode, do you see anything ? |
No errors. Logs for base pull request:
|
And |
Sound like dns issue. i check my setup |
I had the same issue when I installed docker on my 13.04 a few days ago. Try to add |
Strange:
My hack to get working docker on my kismufi server -> add on /etc/hosts
I have no idea why dns resolution doesn't work with docker on my server (nsloookup is ok) |
Solved ! it's ovh ubuntu 13.10 image , if i remove bind9 and resolvconf (aptitude remove bind9 resolvconf) and create /etc/resolv.conf it's works |
What if I want to use bind9 with docker? I have only one dev machine and can't turn of the dns. |
@kthakore: try to add |
No luck On Tue, Nov 26, 2013 at 5:52 PM, Jérôme Petazzoni
|
Ah! |
I can do that! Thx On Sun, Dec 1, 2013 at 7:26 PM, Jérôme Petazzoni notifications@github.com
|
Done. https://groups.google.com/forum/#!topic/docker-user/_xcG8eeg2Ks On Mon, Dec 2, 2013 at 2:17 PM, Kartik Thakore thakore.kartik@gmail.comwrote:
|
This might be an issue again, or possibly a new issue? I'm also on OVH. I removed bind9/resolvconf and updated /etc/resolv.conf with no effect.
|
@hughes Maybe try restarted the docker daemon after you update your dns settings. |
@crosbymichael that did it, thanks for the tip. |
Well, running Docker 0.8, I still get this annoying error. It may be related to the exact network I'm on at the moment, but nslookup, http, and everything else works. Odd docker thing. It does seem to DNS related, but in an odd way. This was at a coffeeshop. It failed $ docker run ubuntu date Unable to find image 'ubuntu' (tag: latest) locally Pulling repository ubuntu 2014/02/11 17:25:29 pull: Get https://index.docker.io/v1/repositories/ubuntu/images: dial tcp: lookup index.docker.io: no DNS servers $ nslookup index.docker.io Server: 172.19.245.1 Address: 172.19.245.1#53 Non-authoritative answer: index.docker.io canonical name = edge-dockerio.dotcloud.com. Name: edge-dockerio.dotcloud.com Address: 54.224.119.89 Name: edge-dockerio.dotcloud.com Address: 54.234.135.251 This was elsewhere and it succeeded $ nslookup index.docker.io Server: 75.75.75.75 Address: 75.75.75.75#53 Non-authoritative answer: index.docker.io canonical name = edge-dockerio.dotcloud.com. Name: edge-dockerio.dotcloud.com Address: 54.234.135.251 Name: edge-dockerio.dotcloud.com Address: 54.224.119.89 So, er, huh. |
+1 on this, using the OSX boot2docker setup and 0.8. |
Update- flushed my DNS cache, restart boot2docker, success. Macintosh:docker brent$ sudo killall -HUP mDNSResponder
Macintosh:docker brent$ boot2docker restart |
I'm having the same issue running coreos inside a vagrant machine (osx host). The solution was to restart docker service:
|
@bbradbury +1, works by flush dns and restart. |
@kthakore, anybody on OVH and anybody who wants to continue running Bind9: I solved the problem by
|
@bryanlarsen +1 ! |
i solved this by adding:
to Hope this helps someone. Running ubuntu 14.04 LTS from OVH |
By the way, I still don't understand what happened. If someone knows and would be kind enough to explain that would be much appreciated. Why is it specific to OVH servers (and in my case, to Kimsufi too)? |
They have their own distribution. I am betting on a custom kernel and setup of the networking, although im unqualified to prove such. I had trouble installing Xen and configuring grub (selecting the kernel). That may be related too. Matej Kramny On Monday, 16 June 2014 at 21:33, Julien Bisconti wrote:
|
@matejkrammy, resolv.conf gets overwritten on reboot in Ubuntu, so your solution is only temporary. Maybe that's what you wanted. |
I added some information and resolutions to docker DNS issues on OVH on my blog at http://soryy.com/ That should help you poor souls out a bit. 😄 |
@matejkramny It is true that they use a modified custom kernel on OVH/Kimsufi but the problem happens even with generic kernel ▶ uname -r
3.13.0-29-generic And I'm on a Ubuntu 14.04 @momer Thank you for the blog post. Although I noticed you added Google name server (
And I still don't understand why docker has a DNS problem... |
@veggiemonk as I mentioned in the post, I was having issues resolving DNS within my containers; adding Google DNS was a fine solution for me. Additionally, adding loop back alone to resolvconf didn't resolve all my issues, even when combined with the --DNS options. Do you run your own DNS? Do you really care that it's being routed through Google? Honestly, in most cases, being concerned about performance there is sort of YAGNI. I'm not saying it's a perfect solution, but it certainly is an OK temp solution. |
These are network problems and not exactly Docker bugs. I'll close this now since this isn't immediately actionable. Please feel free to comment if you've run into this problem or if you think this should remain open. Thanks. |
I believe that to be a misunderstanding. The problem is that Docker (or the network library Docker uses) uses a different way of resolving hostnames than other applications. Whereas every application on a machine can resolve index.docker.io just fine, Docker fails. My guess is that for some odd reason it does not use the standard C |
This has been fixed by switching to Go 1.3 and the next Docker release shouldn't be running into this problem any more. |
@unclejack can you expand on the specific changes which were made? I imagine it has to do with the bridge that's created? |
I am still having the problem with Docker 1.3.1 build 4e9bbfa, on a "VPS Cloud" from OVH.
And resolving indox.docker.io from command line is OK, whereas it is not for Docker. I also tried to add I have nothing in the |
In my post at http://soryy.com/blog/2014/docker-resolving-dns-issues-on-ovh/ (also posted above...), the first point is, "However, you should never use the OVH custom kernel if you plan on using linux containers." |
Also, I would suggest that this is not a docker issue, but a kernel config / OVH networking issue |
It finally worked for me having changed the kernel of my VPS from OVH custom one to Ubuntu default one, like described in comment from Stalbe in issue 4666 My synthesis (in french) Docker + VPS Cloud OVH |
+1 for @matejkramny suggestion, it worked for me too. I had to flush cache http://osxdaily.com/2008/03/21/how-to-flush-your-dns-cache-in-mac-os-x/ and restart with |
I got this error. I tried adding to /etc/resolv.conf with no luck. I then found http://askubuntu.com/questions/130452/how-do-i-add-a-dns-server-via-resolv-conf ... which said "If you really want to add more entries to /etc/resolv.conf, create a /etc/resolvconf/resolv.conf.d/tail and add them there." ...which worked. |
i am trying to login on remote docker resgitry..in this case password is incorrect.. result but again if i run same command with incorrect password Error response from daemon: Get https://index.docker.io/v1/users/: dial tcp: lookup index.docker.io: Temporary failure in name resolution is there any way to get last line or error message..? |
After adding the name servers. I restarted docker/docker-machine and it worked. |
Hi,
I'm using last master and current v0.5.2 version on ubuntu 13.04 (clean install) with 3.8.0-27-generic kernel.
When i pull image from repository i haven't any output and no errors :
And with hello world command :
It's not an network issue because curl https://index.docker.io/v1/repositories/ubuntu/images return json. I tested on another ubuntu it's work. I would like to know why isn't working on this server?
Thank you !
The text was updated successfully, but these errors were encountered: