Can't pull image on my ubuntu 13.04

[dgoujard]

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 :

root@ks3354934:~# docker pull ubuntu
Pulling repository ubuntu
root@ks3354934:~#

And with hello world command :

root@ks3354934:~# docker run -i -t ubuntu /bin/bash                             
Pulling repository ubuntu
2013/08/09 13:36:51 Error: No such image: ubuntu
root@ks3354934:~#

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 !

[vieux]

Maybe you have ufw enabled ?

[dgoujard]

@vieux
No :(

root@ks3354934:~# ufw status verbose
État : inactif

[vieux]

If you launch the daemon in debug mode, do you see anything ?

[dgoujard]

No errors. Logs for base pull request:

2013/08/09 15:00:47 Listening for HTTP on /var/run/docker.sock (unix)
[debug] api.go:920 Registering GET, /containers/{name:.*}/changes
[debug] api.go:920 Registering GET, /images/search
[debug] api.go:920 Registering GET, /containers/json
[debug] api.go:920 Registering GET, /containers/{name:.*}/export
[debug] api.go:920 Registering GET, /containers/{name:.*}/json
[debug] api.go:920 Registering GET, /info
[debug] api.go:920 Registering GET, /version
[debug] api.go:920 Registering GET, /images/viz
[debug] api.go:920 Registering GET, /containers/ps
[debug] api.go:920 Registering GET, /containers/{name:.*}/top
[debug] api.go:920 Registering GET, /events
[debug] api.go:920 Registering GET, /images/json
[debug] api.go:920 Registering GET, /images/{name:.*}/history
[debug] api.go:920 Registering GET, /images/{name:.*}/json
[debug] api.go:920 Registering POST, /images/{name:.*}/insert
[debug] api.go:920 Registering POST, /containers/{name:.*}/restart
[debug] api.go:920 Registering POST, /images/getCache
[debug] api.go:920 Registering POST, /containers/create
[debug] api.go:920 Registering POST, /containers/{name:.*}/kill
[debug] api.go:920 Registering POST, /containers/{name:.*}/start
[debug] api.go:920 Registering POST, /containers/{name:.*}/stop
[debug] api.go:920 Registering POST, /containers/{name:.*}/resize
[debug] api.go:920 Registering POST, /auth
[debug] api.go:920 Registering POST, /build
[debug] api.go:920 Registering POST, /containers/{name:.*}/wait
[debug] api.go:920 Registering POST, /containers/{name:.*}/attach
[debug] api.go:920 Registering POST, /commit
[debug] api.go:920 Registering POST, /images/create
[debug] api.go:920 Registering POST, /images/{name:.*}/push
[debug] api.go:920 Registering POST, /images/{name:.*}/tag
[debug] api.go:920 Registering DELETE, /containers/{name:.*}
[debug] api.go:920 Registering DELETE, /images/{name:.*}
[debug] api.go:920 Registering OPTIONS, 
[debug] api.go:926 Calling POST /images/create from @
2013/08/09 15:00:56 POST /v1.4/images/create?fromImage=base&tag=

[vieux]

And docker search ubuntu ?

[dgoujard]

root@ks3354934:~# docker search ubuntu
2013/08/09 15:05:35 Error: Get https://index.docker.io/v1/search?q=ubuntu: lookup index.docker.io.: no DNS servers

Sound like dns issue. i check my setup

[adrien-f]

I had the same issue when I installed docker on my 13.04 a few days ago.

Try to add nameserver 8.8.8.8 and nameserver 8.8.4.4 to your /etc/resolv.conf, this fixed it for me.

[dgoujard]

Strange:

root@ks3354934:~# nslookup index.docker.io
Server:     127.0.0.1
Address:    127.0.0.1#53

Non-authoritative answer:
index.docker.io canonical name = edge-docker.dotcloud.com.
Name:   edge-docker.dotcloud.com
Address: 54.224.119.89
Name:   edge-docker.dotcloud.com
Address: 54.234.135.251

root@ks3354934:~# docker search ubuntu
2013/08/09 15:12:22 Error: Get https://index.docker.io/v1/search?q=ubuntu: lookup index.docker.io.: no DNS servers

root@ks3354934:~# curl https://index.docker.io/v1/search?q=ubuntu: 
{"query": "ubuntu:", "num_results": 3, "results": [{"name": "jtgeibel/ubuntu", "description": "ubuntu:precise with the precise-security repo enabled"}, {"name": "jtgeibel/ruby", "description": "Based on ubuntu:precise with all of the latest MRI patch levels of 2.0.0, 1.9.3, and 1.8.7."}, {"name": "ipmb/salt-minion", "description": "salt-minion on ubuntu:precise"}]}

My hack to get working docker on my kismufi server -> add on /etc/hosts

54.224.119.89   index.docker.io
54.224.119.89   registry-1.docker.io

I have no idea why dns resolution doesn't work with docker on my server (nsloookup is ok)

[dgoujard]

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

[kthakore]

What if I want to use bind9 with docker? I have only one dev machine and can't turn of the dns.

[jpetazzo]

@kthakore: try to add nameserver 127.0.0.1 to /etc/resolv.conf, that might help.

[kthakore]

No luck

On Tue, Nov 26, 2013 at 5:52 PM, Jérôme Petazzoni
notifications@github.comwrote:

@kthakore https://github.com/kthakore: try to add nameserver 127.0.0.1to
/etc/resolv.conf, that might help.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1470#issuecomment-29343267
.

[jpetazzo]

Ah!
Well, since this issue started with something about Docker 0.5.2, and you are (obviously) not running that version, I think we should move the conversation elsewhere...
Do you think you could ask your question again, either on the docker-user mailing list, or maybe on stack overflow?
You will need to tell exactly how your docker host is configured (bind9, right?), the content of /etc/resolv.conf, the exact problem that you see...
Sorry that I couldn't find a better solution; we will need to get some outside help!

[kthakore]

I can do that! Thx

On Sun, Dec 1, 2013 at 7:26 PM, Jérôme Petazzoni notifications@github.com
wrote:

Ah!
Well, since this issue started with something about Docker 0.5.2, and you are (obviously) not running that version, I think we should move the conversation elsewhere...
Do you think you could ask your question again, either on the docker-user mailing list, or maybe on stack overflow?
You will need to tell exactly how your docker host is configured (bind9, right?), the content of /etc/resolv.conf, the exact problem that you see...

Sorry that I couldn't find a better solution; we will need to get some outside help!

Reply to this email directly or view it on GitHub:
#1470 (comment)

[kthakore]

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:

I can do that! Thx

On Sun, Dec 1, 2013 at 7:26 PM, Jérôme Petazzoni <notifications@github.com

wrote:

Ah!
Well, since this issue started with something about Docker 0.5.2, and you
are (obviously) not running that version, I think we should move the
conversation elsewhere...
Do you think you could ask your question again, either on the docker-user
mailing list, or maybe on stack overflow?
You will need to tell exactly how your docker host is configured (bind9,
right?), the content of /etc/resolv.conf, the exact problem that you see...
Sorry that I couldn't find a better solution; we will need to get some
outside help!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1470#issuecomment-29588020
.

[hughes]

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.

15:09 ~ > docker search ubuntu
2014/01/04 15:09:25 Error: Get https://index.docker.io/v1/search?q=ubuntu: dial tcp: lookup index.docker.io: no DNS servers
15:09 ~ > curl  https://index.docker.io/v1/search?q=ubuntu
{"query": "ubuntu", "num_results": 25 ...}

[crosbymichael]

@hughes Maybe try restarted the docker daemon after you update your dns settings.

[hughes]

@crosbymichael that did it, thanks for the tip.

[merriam]

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.

[bbradbury]

+1 on this, using the OSX boot2docker setup and 0.8.

[bbradbury]

Update- flushed my DNS cache, restart boot2docker, success.

Macintosh:docker brent$ sudo killall -HUP mDNSResponder
Macintosh:docker brent$ boot2docker restart

[bpinto]

I'm having the same issue running coreos inside a vagrant machine (osx host).

The solution was to restart docker service:

sudo systemctl restart docker.service

[jianjin]

@bbradbury +1, works by flush dns and restart.

[bryanlarsen]

@kthakore, anybody on OVH and anybody who wants to continue running Bind9:

I solved the problem by

• adding dns-nameservers 127.0.0.1 to the eth0 section of /etc/network/interfaces
• ifdown eth0 && ifup eth0
• /sbin/restart docker

[thierrystiegler]

@bryanlarsen +1 !

[momer]

👍 @bryanlarsen

[matejkramny]

i solved this by adding:

nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4

to /etc/resolv.conf

Hope this helps someone. Running ubuntu 14.04 LTS from OVH

[veggiemonk]

👍 @bryanlarsen

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)?

[matejkramny]

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:

@bryanlarsen (https://github.com/bryanlarsen)
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)?

—
Reply to this email directly or view it on GitHub (#1470 (comment)).

[bryanlarsen]

@matejkrammy, resolv.conf gets overwritten on reboot in Ubuntu, so your solution is only temporary. Maybe that's what you wanted.

[momer]

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. 😄

[veggiemonk]

@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 (dns-nameservers 127.0.0.1 8.8.8.8 8.8.4.4) in /etc/network/interfaces. Which means that every dns request on your server may be redirected to Google NS... @bryanlarsen's solution is the cleanest so far by just adding dns-nameservers 127.0.0.1 to /etc/network/interfaces and setting /etc/default/docker.io:

DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4"

And I still don't understand why docker has a DNS problem...

[momer]

@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.

[unclejack]

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.

[CyberShadow]

These are network problems and not exactly Docker bugs.

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 getaddrinfo function.

[unclejack]

This has been fixed by switching to Go 1.3 and the next Docker release shouldn't be running into this problem any more.

[momer]

@unclejack can you expand on the specific changes which were made? I imagine it has to do with the bridge that's created?

[mfaure]

I am still having the problem with Docker 1.3.1 build 4e9bbfa, on a "VPS Cloud" from OVH.

~# docker search ubuntu
2014/11/15 09:06:55 Error response from daemon: Get https://index.docker.io/v1/search?q=ubuntu: dial tcp: lookup index.docker.io: no DNS servers

And resolving indox.docker.io from command line is OK, whereas it is not for Docker.

I also tried to add DOCKER_OPTS="--dns 127.0.0.1 --dns 213.186.33.99" to /etc/default/docker but that does not work either.

I have nothing in the /etc/resolv.conf but adding @bryanlarsen's solution prevents the vps from booting correctly (!) (needs further investigations)

[momer]

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."

[momer]

Also, I would suggest that this is not a docker issue, but a kernel config / OVH networking issue

[mfaure]

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

[saxxi]

+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 boot2docker restart as well.

[NigelThorne]

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.

[sanjaykumarjha]

i am trying to login on remote docker resgitry..in this case password is incorrect..
[root@admin ~]# docker login -e testid@gmail.com -u test -p xyzz

result
Error response from daemon: Wrong login/password, please try again

but again if i run same command with incorrect password
why docker shows below line of error message..why error message get changed by this line

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..?

[avramirez]

After adding the name servers. I restarted docker/docker-machine and it worked.