Remove instruction to append DockerInsecureRegistryAddress
This is now done automatically by the prepare command that detects if the registry is secure and appends DockerInsecureRegistryAddress when needed. Change-Id: I0c34cc86703888089b20e90accef9ab2c417bf8a Depends-On: I74586145c222921880402cec92bbaa5f10e8b972 Related-Bug: #1722632
This commit is contained in:
parent
445ef69543
commit
9a0ef0cc65
@ -108,12 +108,6 @@ containers available in the local registry::
|
|||||||
--tag latest \
|
--tag latest \
|
||||||
--env-file ~/docker_registry.yaml
|
--env-file ~/docker_registry.yaml
|
||||||
|
|
||||||
For development we also set the registry as insecure so we do not need to deal
|
|
||||||
with TLS configurations::
|
|
||||||
|
|
||||||
echo " DockerInsecureRegistryAddress: 192.168.24.1:8787" >> \
|
|
||||||
~/docker_registry.yaml
|
|
||||||
|
|
||||||
|
|
||||||
Deploying the containerized Overcloud
|
Deploying the containerized Overcloud
|
||||||
-------------------------------------
|
-------------------------------------
|
||||||
|
Loading…
x
Reference in New Issue
Block a user