From 5b329741e39f157958839e6637b42619bb7c08c1 Mon Sep 17 00:00:00 2001
From: "wu.chunyang" <wuchunyang@yovole.com>
Date: Thu, 25 Aug 2022 23:16:55 +0800
Subject: [PATCH] [doc] Run docker registry with host network
As we disabled docker bridge network, we should run docker registry
with host network now.
Change-Id: I4cc4175ddc9b90847bf956007e2b9fe803960651
---
doc/source/user/multinode.rst | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/source/user/multinode.rst b/doc/source/user/multinode.rst
index 8e28197dbc..5074fa728b 100644
--- a/doc/source/user/multinode.rst
+++ b/doc/source/user/multinode.rst
@@ -20,14 +20,15 @@ A very simple registry may be deployed on the current host as follows:
.. code-block:: console
docker run -d \
+ --network host \
--name registry \
--restart=always \
- -p 4000:5000 \
+ -e REGISTRY_HTTP_ADDR=0.0.0.0:4000 \
-v registry:/var/lib/registry \
registry:2
Here we are using port 4000 to avoid a conflict with Keystone. If the registry
-is not running on the same host as Keystone, the ``-p`` argument may be
+is not running on the same host as Keystone, the ``-e`` argument may be
omitted.
Edit ``globals.yml`` and add the following, where ``192.168.1.100:4000`` is the