[tripleo_podman] Add network_backend section in containers.conf

c599369842 (diff-553c14d0ba1ded3ba9cc0026de8bcba3df444cde5212d8438932fa58246901fbR281)
provides a way to use cni or netavark as a network backend
with podman.

With podman-4.0 in RHEL-9, netavark is used. This changes makes it
configurable.

Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I756365162e4bf435adbb2cc32b1dc7a31a7e950d
This commit is contained in:
Chandan Kumar (raukadah) 2022-06-03 19:09:11 +05:30
parent 56e724ad53
commit 1ae9a33e1a
3 changed files with 5 additions and 0 deletions

View File

@ -80,4 +80,5 @@ tripleo_podman_registries: []
tripleo_container_default_pids_limit: 4096
tripleo_container_events_logger_mechanism: journald
tripleo_container_default_runtime: runc
tripleo_container_default_network_backend: "cni"
tripleo_container_default_infra_image: "registry.access.redhat.com/ubi8/pause"

View File

@ -97,6 +97,9 @@
- section: engine
option: infra_image
value: "\"{{ tripleo_container_default_infra_image }}\""
- section: network
option: network_backend
value: "\"{{ tripleo_container_default_network_backend }}\""
- name: Enable podman.socket service
when:

View File

@ -21,3 +21,4 @@ _tripleo_buildah_packages:
- buildah
tripleo_container_default_runtime: crun
tripleo_container_default_network_backend: "netavark"