Răsfoiți Sursa

Now with TLS, but somehow not client auth

Zach Isbach 4 ani în urmă
părinte
comite
9d3e75a8de
1 a modificat fișierele cu 10 adăugiri și 6 ștergeri
  1. 10 6
      plays/docker/service.yaml

+ 10 - 6
plays/docker/service.yaml

@@ -7,12 +7,9 @@
       name: registry
       image: registry:2
       env:
-#        REGISTRY_HTTP_ADDR: '0.0.0.0:443'
-#        REGISTRY_HTTP_TLS_CERTIFICATE: /certs/domain.crt
-#        REGISTRY_HTTP_TLS_KEY: /certs/domain.key
-#        REGISTRY_HTTP_TLS_LETSENCRYPT_CACHEFILE: /var/lib/registry/letsencrypt
-#        REGISTRY_HTTP_TLS_LETSENCRYPT_EMAIL: letsencrypt@zi3.fi
-#        REGISTRY_HTTP_TLS_LETSENCRYPT_HOSTS_0: registry.docker.aws.zi3.fi
+        REGISTRY_HTTP_TLS_CERTIFICATE: /certs/fullchain.pem
+        REGISTRY_HTTP_TLS_KEY: /certs/privkey.pem
+        REGISTRY_HTTP_TLS_CLIENTCAS_0: /certs/ca.pem
       publish: [
         { published_port: 5000, target_port: 5000 }
       ]
@@ -23,5 +20,12 @@
           source: docker_registry/data,
           target: /var/lib/registry,
           readonly: no,
+        },
+        {
+          type: volume,
+          driver_config: { name: glusterfs },
+          source: docker_registry/certs,
+          target: /certs,
+          readonly: yes,
         }
       ]