You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After looking at the following code for the podman task codes, I see that the value of __podman_service_name is automatically suffixed with .volume. podman/tasks/handle_quadlet_spec.yml
else __podman_quadlet_name ~ '.volume'
But according to the podman-systemd documentation, the Volume unit automatically creates service name with the -volume.service suffix.
I added "activate_systemd_unit: false" to quadlet_specs to skip the play to start the service, but I think the code should be changed to: else __podman_quadlet_name ~ '-volume'
Right?
The text was updated successfully, but these errors were encountered:
I used such a volume file to create a volume for the promtail container:
The contents of the promtail-data.volume file are only:
[Volume]
But when I run the ansible play, the following error is reported:
TASK [ansible-role-podman : Start service] *****************************************************************************************************************
fatal: [my-hostname]: FAILED! => {
"changed": false,
"invocation": {
"module_args": {
"daemon_reexec": false,
"daemon_reload": false,
"enabled": null,
"force": null,
"masked": null,
"name": "promtail-data.volume",
"no_block": false,
"scope": "system",
"state": "started"
}
},
"msg": "Could not find the requested service promtail-data.volume: host"
}
After looking at the following code for the podman task codes, I see that the value of __podman_service_name is automatically suffixed with .volume.
podman/tasks/handle_quadlet_spec.yml
But according to the podman-systemd documentation, the Volume unit automatically creates service name with the -volume.service suffix.
I added "activate_systemd_unit: false" to quadlet_specs to skip the play to start the service, but I think the code should be changed to:
else __podman_quadlet_name ~ '-volume'
Right?
The text was updated successfully, but these errors were encountered: