From 603690eade384a6bdd024255196edb1c7010bc23 Mon Sep 17 00:00:00 2001 From: Sajay Antony Date: Wed, 8 Feb 2017 14:10:37 -0800 Subject: [PATCH] Updating custom domain docs. --- docs/Troubleshooting Guide.md | 2 +- docs/custom-domain.md | 2 +- docs/custom-domain/docker-compose.yml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Troubleshooting Guide.md b/docs/Troubleshooting Guide.md index c76b69c..0ab9393 100644 --- a/docs/Troubleshooting Guide.md +++ b/docs/Troubleshooting Guide.md @@ -44,4 +44,4 @@ docker login .azurecr.io # How to use a custom domain for azure container registry -Azure docker registries has a typical login url of the format `*.azurecr.io`. A customer might like to have a custom domain that associate with its own organization. Follow [this guide](custom-domain.md) to achieve that. +Azure docker registries has a typical login url of the format `*.azurecr.io`. A customer might like to have a custom domain for the registry. Follow [this guide](custom-domain.md) to achieve that. diff --git a/docs/custom-domain.md b/docs/custom-domain.md index 87ed33d..2351314 100644 --- a/docs/custom-domain.md +++ b/docs/custom-domain.md @@ -14,7 +14,7 @@ To setup custom domain for azure container registry, the following prerequisites 1. On `registry.contoso.com`, copy [setup files](custom-id/) into it. 2. Create a sub-directory named `ssl`, copy `cert.crt`, `private.key`, and `pwd` into this directory. The location of these files can be changed but volume entries in the [docker-compose.yml](custom-id/docker-compose.yml#L11-L13) would then need to be updated to reflect the changes. -3. Edit [custom_id.env](custom-id/custom_id.env) to point to your front end docker host (E.g. `registry.contoso.com`) and backend Azure Docker Registry (E.g. `peterhsuacr-microsoft.azurecr.io`). +3. Edit [custom_domain.env](custom-domain/custom_domain.env) to point to your front end docker host (E.g. `registry.contoso.com`) and backend Azure Docker Registry (E.g. `peterhsuacr-microsoft.azurecr.io`). 4. Run `docker-compose up -d` and this should bring up the nginx service that would forward all docker requests from your front end service to the backend Azure Docker Registry. ## Quick verification diff --git a/docs/custom-domain/docker-compose.yml b/docs/custom-domain/docker-compose.yml index 79f6224..1a83d54 100644 --- a/docs/custom-domain/docker-compose.yml +++ b/docs/custom-domain/docker-compose.yml @@ -5,7 +5,7 @@ proxy: - 443:443 env_file: - - custom_id.env + - custom_domain.env volumes: - ./ssl/cert.crt:/etc/nginx/ssl/cert.crt:ro