Browse Source

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
changes/47/800847/1
David Vallee Delisle 2 months ago
parent
commit
7f5ecb62b5
  1. 5
      releasenotes/notes/tripleo-podman-enable_socket-f93bdaa47f4b01d9.yaml
  2. 1
      tripleo_ansible/roles/tripleo_podman/defaults/main.yml
  3. 8
      tripleo_ansible/roles/tripleo_podman/tasks/tripleo_podman_install.yml

5
releasenotes/notes/tripleo-podman-enable_socket-f93bdaa47f4b01d9.yaml

@ -0,0 +1,5 @@
---
features:
- |
tripleo-podman now has the ability to enable podman.socket service when
tripleo_podman_enable_socket is enabled.

1
tripleo_ansible/roles/tripleo_podman/defaults/main.yml

@ -27,6 +27,7 @@ tripleo_podman_packages: "{{ _tripleo_podman_packages | default([]) }}"
tripleo_buildah_packages: "{{ _tripleo_buildah_packages | default([]) }}"
tripleo_podman_purge_packages: "{{ _tripleo_podman_purge_packages | default([]) }}"
tripleo_podman_tls_verify: true
tripleo_podman_enable_socket: false
tripleo_podman_unqualified_search_registries:
- registry.redhat.io
- registry.access.redhat.com

8
tripleo_ansible/roles/tripleo_podman/tasks/tripleo_podman_install.yml

@ -80,3 +80,11 @@
- section: engine
option: events_logger
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…
Cancel
Save