From dddfe6cf709ccb2aa85533aae183caebafc1c521 Mon Sep 17 00:00:00 2001 From: Akshay Date: Mon, 10 Jan 2022 08:38:02 +0100 Subject: [PATCH] Issue-#852: Add content --- content/tutorials/compute-to-data-docker-registry.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/tutorials/compute-to-data-docker-registry.md b/content/tutorials/compute-to-data-docker-registry.md index 951ffd70..8a1e3ac5 100644 --- a/content/tutorials/compute-to-data-docker-registry.md +++ b/content/tutorials/compute-to-data-docker-registry.md @@ -7,16 +7,16 @@ The tutorial provides the steps to setup a private docker registry on the server To implement this use case, 2 domains will be required: -- **example.com**: This domain will allow only image pull operations +- **example.com**: This domain will allow only image pull operations - **admin.example.com**: This domain will allow image push/pull operations only to the authenticated users. _Note: Please change the domain names to your application-specific domain names._ ## Prerequisites -1. Running docker environment on the linux server. -2. 2 domain names is mapped to the same server IP address. -3. SSL certificate +- Running docker environment on the linux server. +- Docker compose is installed. +- 2 domain names is mapped to the same server IP address. ## Generate certificates @@ -90,6 +90,8 @@ services: ## Nginx configuration +Copy the below nginx configuration to a `nginx.conf` file. + ```conf events {} http {