Nginx反向代理Docker registry SSL

nginx和docker registry都需要設(shè)置證書
nginx配置文件如下
upstream my_docker_registry {
ip_hash;
server 127.0.0.1:32773;
server 127.0.0.1:32774;
server 127.0.0.1:32775;
#server 127.0.0.1:32770;
}

server {
listen 5000 ssl;
server_name registry.vrviu.com;
ssl_certificate /export/registry_ssl_certs/registry.v.com.crt;
ssl_certificate_key /export/registry_ssl_certs/registry.v.com.key;
client_max_body_size 0;
# disable any limits to avoid HTTP 413 for large image uploads
# required to avoid HTTP 411: see Issue #1486 (https://github.com/docker/docker/issues/1486)
chunked_transfer_encoding on;

    location / {
            proxy_pass  https://my_docker_registry;
            proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
            proxy_redirect off;
            proxy_buffering off;
            proxy_set_header        X-Real-IP       $remote_addr;
            proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header        Host            $host;
            proxy_set_header  X-Forwarded-Proto $scheme;
    }

}

參考:https://docs.docker.com/registry/recipes/nginx/#starting-and-stopping
http://blog.csdn.net/renhuailin/article/details/50461651
http://www.cnblogs.com/highend/p/docker_registry_push_error_blob-upload-unknown.html

最后編輯于
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成,瀏覽時(shí)請結(jié)合常識與多方信息審慎甄別。
平臺(tái)聲明:文章內(nèi)容(如有圖片或視頻亦包括在內(nèi))由作者上傳并發(fā)布,文章內(nèi)容僅代表作者本人觀點(diǎn),簡書系信息發(fā)布平臺(tái),僅提供信息存儲(chǔ)服務(wù)。

相關(guān)閱讀更多精彩內(nèi)容

友情鏈接更多精彩內(nèi)容