docker_registry must use host network
This ensures we won't crash on netavark rules in the firewall, especially since we're flushing everything when we load nftables ruleset. Closes-Bug: #1991868 Depends-On: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/860824 Change-Id: I727dd5598e95657f35ea8e4fe6d51516ee63272d
This commit is contained in:
parent
db86a9352b
commit
048667a14d
|
@ -21,8 +21,8 @@
|
|||
shell: >-
|
||||
podman run
|
||||
-d
|
||||
--network=host
|
||||
--name docker_registry
|
||||
-p {{ content_provider_registry_port }}:{{ content_provider_registry_port }}
|
||||
-e REGISTRY_HTTP_ADDR="0.0.0.0:{{ content_provider_registry_port }}"
|
||||
-e REGISTRY_LOG_LEVEL=debug
|
||||
{{ container_registry_image }}
|
||||
|
@ -34,8 +34,8 @@
|
|||
shell: >-
|
||||
podman run
|
||||
-d
|
||||
--network=host
|
||||
--name docker_registry
|
||||
-p {{ content_provider_registry_port }}:{{ content_provider_registry_port }}
|
||||
-e REGISTRY_HTTP_ADDR="0.0.0.0:{{ content_provider_registry_port }}"
|
||||
-e REGISTRY_LOG_LEVEL=debug
|
||||
{{ container_registry_image_fallback }}
|
||||
|
|
Loading…
Reference in New Issue