From 2bd36e15a2e27cd2dd0d7a936a5fe8684d8624ef Mon Sep 17 00:00:00 2001 From: Akshay Date: Mon, 10 Jan 2022 08:31:11 +0100 Subject: [PATCH] Issue-#852: Add content --- content/tutorials/compute-to-data-docker-registry.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/tutorials/compute-to-data-docker-registry.md b/content/tutorials/compute-to-data-docker-registry.md index 290c1282..951ffd70 100644 --- a/content/tutorials/compute-to-data-docker-registry.md +++ b/content/tutorials/compute-to-data-docker-registry.md @@ -7,26 +7,27 @@ 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 -- admin.example.com: This domain will allow image push/pull operations only to the authenticated users. +- **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 server. +1. Running docker environment on the linux server. 2. 2 domain names is mapped to the same server IP address. 3. SSL certificate ## Generate certificates - ```bash # install certbot: https://certbot.eff.org/ sudo certbot certonly --standalone --cert-name example.com -d example.com sudo certbot certonly --standalone --cert-name admin.example.com -d admin.example.com ``` +_Note: Do check the access right of the files/directories where certificates are stored. Usually, they are at `/etc/letsencrypt/`._ + ## Generate password file Replace content in `<>` with appropriate content.