![如何使用 nginx 配置 docker 注册表](https://linux22.com/image/1008647/%E5%A6%82%E4%BD%95%E4%BD%BF%E7%94%A8%20nginx%20%E9%85%8D%E7%BD%AE%20docker%20%E6%B3%A8%E5%86%8C%E8%A1%A8.png)
我配置了一个私有的docker registry server来存储镜像,我是Ubuntu 18.04。
我在 nginx 容器和 registry 容器之间的交互中遇到了问题。
运行推送镜像时速度非常慢。问题如下。
$ 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
进程正在进行,但速度非常慢。发送 100 KB 并等待 15 秒。然后再次发送。
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;
}
}
如果您从容器注册表打开端口,docker push 可以正常工作。我猜问题出在我的 nginx 设置上,但也可能不是。
为了测试,我创建了一个项目 https://bitbucket.org/mrvstas/registry-docker
有人遇到过类似情况吗? nginx 怎么办? docker registry 怎么办?
答案1
我遇到了一个非常相似的问题,结果发现是由 引起的proxy_set_header X-Forwarded-Proto $scheme;
。我有两层代理,docker-registry 前面的 nginx 最终设置X-Forwarded-Proto
为“http”,尽管最终docker push
是通过“https”访问它的。
删除该行或将其设置为“https”而不是$scheme对我来说都可以,但也许使用map
指令$http_x_forwarded_proto
会更好。
以下是我最终做的事情:
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;
}
}
}