tripleo-podman: Enable and start podman.socket
It might be a good idea to control wether or not the podman.socket service is enabled in case we want to podman --remote. We plan on using this in the wrapper services instead of relying on nsenter. Change-Id: I52d63d34a9c01bac7e77f2ce9154aa719b4f82b5
This commit is contained in:
parent
b1fede276f
commit
7f5ecb62b5
|
@ -0,0 +1,5 @@
|
||||||
|
---
|
||||||
|
features:
|
||||||
|
- |
|
||||||
|
tripleo-podman now has the ability to enable podman.socket service when
|
||||||
|
tripleo_podman_enable_socket is enabled.
|
|
@ -27,6 +27,7 @@ tripleo_podman_packages: "{{ _tripleo_podman_packages | default([]) }}"
|
||||||
tripleo_buildah_packages: "{{ _tripleo_buildah_packages | default([]) }}"
|
tripleo_buildah_packages: "{{ _tripleo_buildah_packages | default([]) }}"
|
||||||
tripleo_podman_purge_packages: "{{ _tripleo_podman_purge_packages | default([]) }}"
|
tripleo_podman_purge_packages: "{{ _tripleo_podman_purge_packages | default([]) }}"
|
||||||
tripleo_podman_tls_verify: true
|
tripleo_podman_tls_verify: true
|
||||||
|
tripleo_podman_enable_socket: false
|
||||||
tripleo_podman_unqualified_search_registries:
|
tripleo_podman_unqualified_search_registries:
|
||||||
- registry.redhat.io
|
- registry.redhat.io
|
||||||
- registry.access.redhat.com
|
- registry.access.redhat.com
|
||||||
|
|
|
@ -80,3 +80,11 @@
|
||||||
- section: engine
|
- section: engine
|
||||||
option: events_logger
|
option: events_logger
|
||||||
value: "\"{{ tripleo_container_events_logger_mechanism }}\""
|
value: "\"{{ tripleo_container_events_logger_mechanism }}\""
|
||||||
|
|
||||||
|
- name: Enable podman.socket service
|
||||||
|
when:
|
||||||
|
- tripleo_podman_enable_socket | bool
|
||||||
|
systemd:
|
||||||
|
name: podman.socket
|
||||||
|
state: started
|
||||||
|
enabled: true
|
||||||
|
|
Loading…
Reference in New Issue