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
TASK [Start the pod] ******************************************************************************************************************************************************fatal: [192.168.33.6]: FAILED! => {"changed": false, "msg": "Can't run container postgresql-sonarqube", "stderr": "Error: the --rm option conflicts with --restart, when the restartPolicy is not \"\" and \"no\"\n", "stderr_lines": ["Error: the --rm option conflicts with --restart, when the restartPolicy is not \"\" and \"no\""], "stdout": "", "stdout_lines": []}
Steps to reproduce the issue:
Use RockyLinux8 image for vagrant
Apply a playbook with the aforementioned task.
See it fail.
Describe the results you received:
TASK [Start the pod] ******************************************************************************************************************************************************fatal: [192.168.33.6]: FAILED! => {"changed": false, "msg": "Can't run container postgresql-sonarqube", "stderr": "Error: the --rm option conflicts with --restart, when the restartPolicy is not \"\" and \"no\"\n", "stderr_lines": ["Error: the --rm option conflicts with --restart, when the restartPolicy is not \"\" and \"no\""], "stdout": "", "stdout_lines": []}
Describe the results you expected:
TASK [Start the pod] ******************************************************************************************************************************************************changed: [192.168.33.6]
Additional information you deem important (e.g. issue happens only occasionally):
Changing version to 1.9.4 fixes the issue, as well as another one that fail to get the diff of the journalctl log level that used to happen on subsequent runs if I wouldn't downgrade. I downgrade the following way:
mkdir -p ~/.ansible/collections/ansible_collections/containers
git clone https://github.com/containers/ansible-podman-collections.git ~/.ansible/collections/ansible_collections/containers/podman
cd ~/.ansible/collections/ansible_collections/containers/podman
git checkout tags/1.9.4
cd -
Checking out to 1.10.1, doesn't fix the issue, though.
Version of the containers.podman collection: 1.10.1
Command line and output of ansible run with high verbosity
Note that I had to rerun the command after having already succesfully started the postgres-sonarqube container (downgraded back and forth to submit the issue here) and that it therefore failed at the next container instead in the following logs (with exact same error).
Additional environment details (AWS, VirtualBox, physical, etc.):
I'm botting up a vagrant machine from Windows, and I use wsl to run ansible from which I use the vagrant-generated ssh key
The text was updated successfully, but these errors were encountered:
The problem is in duplication of restart_policy both in container and systemd. If you plan to manage containers with systemd, put restart_policy only there.
Systemd flag new implies --rm, and:
--rm is only allowed with on-failure as a restart policy.
as it seems from issue containers/podman#11438
If you remove restart_policy: always from container args and leave it only in systemd, it will work fine.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Unable to apply the following task in a playbook:
It gets me the following error:
Steps to reproduce the issue:
Use RockyLinux8 image for vagrant
Apply a playbook with the aforementioned task.
See it fail.
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Changing version to
1.9.4
fixes the issue, as well as another one that fail to get the diff of the journalctl log level that used to happen on subsequent runs if I wouldn't downgrade. I downgrade the following way:Checking out to
1.10.1
, doesn't fix the issue, though.Version of the
containers.podman
collection: 1.10.1Output of
ansible --version
:Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Playbok you run with ansible (e.g. content of
playbook.yaml
):Command line and output of ansible run with high verbosity
Note that I had to rerun the command after having already succesfully started the postgres-sonarqube container (downgraded back and forth to submit the issue here) and that it therefore failed at the next container instead in the following logs (with exact same error).
Additional environment details (AWS, VirtualBox, physical, etc.):
I'm botting up a vagrant machine from Windows, and I use wsl to run ansible from which I use the vagrant-generated ssh key
The text was updated successfully, but these errors were encountered: