Docker Error: Server Misbehaving

Question

The details:

Client: Docker Enterprise Edition (EE) 2.0
 Version:       17.06.2-ee-10
 API version:   1.30
 Go version:    go1.8.7
 Git commit:    66261a0
 Built: Fri Apr 27 00:38:41 2018
 OS/Arch:       linux/amd64

Server: Docker Enterprise Edition (EE) 2.0
 Engine:
  Version:      17.06.2-ee-10
  API version:  1.30 (minimum version 1.12)
  Go version:   go1.8.7
  Git commit:   66261a0
  Built:        Fri Apr 27 00:40:03 2018
  OS/Arch:      linux/amd64
  Experimental: false 

Kernel Version:

uname -r: 3.10.0-693.21.1.el7.x86_64

Operating System:

 OS: Red Hat 7.4 (maipo)

Docker client was actually unable to connect to Docker Hub to pull the ucp image [#37532]. So we have leveraged docker save and docker load commands. After untarring the tar file using docker load, the ucp image was there.

But we are getting the following error when we run the image:

-bash-4.2$ docker container run --rm -it --name ucp   -v /var/run/docker.sock:/var/run/docker.sock   docker/ucp:3.0.2 install   --host-address <node-ip-addr> --interactive --registry-username [$REGSITRY_PASSWORD] --registry-password [$REGISTRY_USERNAME]
INFO[0000] Your engine version 17.06.2-ee-10, build 66261a0 (3.10.0-693.21.1.el7.x86_64) is compatible with UCP 3.0.2 (736cf3c) 
WARN[0000] Your system uses devicemapper.  We can not accurately detect available storage space.  Please make sure you have at least 3.00 GB available in /var/lib/docker 
Admin Username: admin
Admin Password: 
Confirm Admin Password: 
INFO[0012] Pulling required images... (this may take a while) 
INFO[0012] Pulling docker/ucp-auth:3.0.2                
Please enter your Docker Hub username ([]): ________
Please enter your Docker Hub password (**): 
INFO[0037] Pulling required images... (this may take a while) 
INFO[0037] Pulling docker/ucp-auth:3.0.2                
ERRO[0042] We were unable to pull one or more required images.  Please set REGISTRY_USERNAME and REGISTRY_PASSWORD environment variables for your Docker Hub account on this container with -e flags to run. 
FATA[0042] Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: server misbehaving 
After referring multiple forums and this article, we had added Google's DNS nameservers.

This our resolv.conf file:

-bash-4.2$ cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
#nameserver 127.0.0.1

search 1234.com
nameserver  127.0.0.1
nameserver      xx.xx.xx.xx
nameserver      xx.xx.xx.xx
nameserver     xx.xx.xx.xx

The problem is we can't reboot the server because it sits in our corporate DMZ (behind a proxy), and there are other services running too. So, we really can't reboot the server.

We request the community to provide us a solution.

Thanks and Regards Aditya

Answer 1

Look at this part of your error message. We can not accurately detect available storage space. Please make sure you have at least 3.00 GB available in /var/lib/docker

Try to have more space in /var/lib/docker, mounting other directory / device in this path, with a symlink or whatever that let docker download the image.

Answer 2

@lvthillo

I am answring my own question.

The solution to this problem lies in saving and loading the docker images (including all the sub-dependent images). We had to resort to this method as our servers are behind proxy. The Docker REST API was unable to establish a connection to Docker Hub (outside world). That's why the aforementioned error was surfacing.

The offline method solved our problem. I know it unwieldy, but it is working.

Regards Aditya