I'm using /home/stack/containers-default-parameters.yaml which gets created by quickstart, it looks like:
$ cat /home/stack/containers-default-parameters.yaml
parameter_defaults:
# NovaImage: atomic-image # FYI the team is using overcloud-full currently https://review.openstack.org/#/c/395880/
# Defaults to 'tripleoupstream'. Specify a local docker registry
# Example: 192.0.2.1:8787/tripleoupstream
DockerNamespace: 192.168.24.1:8787/tripleoupstream
# Enable local Docker registry
DockerNamespaceIsRegistry: true
So it does appear to be configured correctly, and the service is listening on the right IP:
$ netstat -taupen | grep 8787
(No info could be read for "-p": geteuid()=1000 but you should be root.)
tcp 0 0 192.168.24.1:8787 0.0.0.0:* LISTEN 0 1352248 -
Also the environment file doesn't solve the case where an operator interacts with docker directly on the CLI (I know we probably don't want to encourage that, but it's useful for developers at least).
I'm using /home/stack/ containers- default- parameters. yaml which gets created by quickstart, it looks like:
$ cat /home/stack/ containers- default- parameters. yaml /review. openstack. org/#/c/ 395880/ 1:8787/ tripleoupstream 24.1:8787/ tripleoupstream ceIsRegistry: true
parameter_defaults:
# NovaImage: atomic-image # FYI the team is using overcloud-full currently https:/
# Defaults to 'tripleoupstream'. Specify a local docker registry
# Example: 192.0.2.
DockerNamespace: 192.168.
# Enable local Docker registry
DockerNamespa
So it does appear to be configured correctly, and the service is listening on the right IP:
$ netstat -taupen | grep 8787
(No info could be read for "-p": geteuid()=1000 but you should be root.)
tcp 0 0 192.168.24.1:8787 0.0.0.0:* LISTEN 0 1352248 -
Also the environment file doesn't solve the case where an operator interacts with docker directly on the CLI (I know we probably don't want to encourage that, but it's useful for developers at least).