How to configure docker registry with nginx

Question

I configure a private docker registry server to store images. I am Ubuntu 18.04.

I have a problem in the interaction between the nginx container and the registry container.

Very slow speed when running a push image. The problem looks like this.

$ docker push 192.168.3.131:6080/my-ubuntu

The push refers to a repository [192.168.3.131:6080/my-ubuntu]
2de391e51d73: Retrying in 14 seconds
d73dd9e65295: Retrying in 14 seconds
686245e78935: Retrying in 14 seconds
d7ff1dc646ba: Retrying in 14 seconds
644879075e24: Retrying in 14 seconds

The process is going on, but very slowly. Send 100 KB and wait for 15 seconds. And then again.

docker-compose

version: '3'

services:
  registry:
    container_name: registry
    restart: always
    image: registry:2
    volumes:
      - /srv/docker-registry/data:/var/lib/registry

  nginx:
    container_name: nginx
    image: nginx
    restart: always
    links:
       - registry
    volumes:
       - "./nginx.conf:/etc/nginx/conf.d"
    ports:
       - "80:80"

networks:
  default:
    external:
      name: nginx-proxy

nginx.conf

map $upstream_http_docker_distribution_api_version $docker_distribution_api_version {
    '' 'registry/2.0';
}

upstream docker-registry {
   server registry:5000;
}

server {
    listen       80;
    server_name  "";

    proxy_send_timeout 120;
    proxy_buffering    off;
    tcp_nodelay        on;

    access_log off;

    # disable any limits to avoid HTTP 413 for large image uploads
    client_max_body_size 0;

    # required to avoid HTTP 411: see Issue #1486 (https://github.com/moby/moby/issues/1486)
    chunked_transfer_encoding on;

    location /v2/ {
        # Do not allow connections from docker 1.5 and earlier
        # docker pre-1.6.0 did not properly set the user agent on ping, catch "Go *" user agents
        if ($http_user_agent ~ "^(docker\/1\.(3|4|5(?!\.[0-9]-dev))|Go ).*$" ) {
            return 404;
        }

        # To add basic authentication to v2 use auth_basic setting.
        auth_basic "Registry realm";
        auth_basic_user_file /etc/nginx/conf.d/nginx.htpasswd;

        ## If $docker_distribution_api_version is empty, the header is not added.
        ## See the map directive above where this variable is defined.
        # add_header 'Docker-Distribution-Api-Version' $docker_distribution_api_version always;

        proxy_pass                          http://docker-registry;
        proxy_set_header  Host              $http_host;   # required for docker client's sake
        proxy_set_header  X-Real-IP         $remote_addr; # pass on real client's IP
        proxy_set_header  X-Forwarded-For   $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto  $scheme;
        proxy_set_header X-Forwarded-Host   $host:$server_port;
        proxy_set_header X-Original-URI     $request_uri;
        proxy_set_header Docker-Distribution-Api-Version registry/2.0;
        proxy_read_timeout                  900;
    }
}

If you open the port from the container registry, docker push works well. I guess the problem is in my settings in nginx, but maybe not.

For testing, I made a project https://bitbucket.org/mrvstas/registry-docker

Can anyone come across a similar? What to do with nginx? What to do with docker registry?

Answer 1

I had a very similar problem that turned out to be caused by proxy_set_header X-Forwarded-Proto $scheme;. I had two layers of proxy, and the nginx in front of docker-registry ended up setting X-Forwarded-Proto to "http" even though ultimately docker push was accessing it over "https".

Either deleting that line, or setting it to "https" instead of $scheme did the trick for me, but perhaps some work with map directive and $http_x_forwarded_proto would be better.

Here's what I ended up doing:

http {

  ...

  # If X-Forwarded-Proto was set, use that, otherwise fallback to
  # $scheme. Used below to set X-Forwarded-Proto when proxying to the
  # registry.
  map $http_x_forwarded_proto $my_scheme {
    default $http_x_forwarded_proto;
    '' $scheme;
  }

  server {
    ...
    location /v2/ {
      ...
      proxy_set_header X-Forwarded-Proto $my_scheme;
    }
  }
}