From 8f8da6a2f4fa6a297c54457a09c351695bc419ff Mon Sep 17 00:00:00 2001 From: Jan Kristof Nidzwetzki Date: Wed, 25 Dec 2019 21:59:10 +0100 Subject: [PATCH] Update private-registries.md --- docs/private-registries.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/private-registries.md b/docs/private-registries.md index 4136c48..4afbb86 100644 --- a/docs/private-registries.md +++ b/docs/private-registries.md @@ -3,21 +3,21 @@ Watchtower supports private Docker image registries. In many cases, accessing a The credentials can be provided to watchtower in a configuration file called `config.json`. There are two ways to generate this configuration file: * The configuration file can be created manually. -* Call `docker login $REGISTRY_NAME` and share the resulting configuration file. +* Call `docker login ` and share the resulting configuration file. ### Create the configuration file manually Create a new configuration file with the following syntax and a base64 encoded username and password `auth` string: ```json { "auths": { - "$REGISTRY_NAME": { + "": { "auth": "XXXXXXX" } } } ``` -`$REGISTRY_NAME` needs to be replaced by the name of your private registry (e.g., `my-private-registry.example.org`) +`` needs to be replaced by the name of your private registry (e.g., `my-private-registry.example.org`) The required `auth` string can be generated as follows: ```bash