-
-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not idemponent when port is bound to 0.0.0.0
#678
Comments
I think it's by default bind to |
Oh yes, your are right, thanks. I started being explicit when I accidentally exposed my services to the public. I will remove the |
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Nov 30, 2023
Fix containers#678 Signed-off-by: Sagi Shnaidman <[email protected]>
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Nov 30, 2023
Fix containers#678 Signed-off-by: Sagi Shnaidman <[email protected]>
sshnaidm
added a commit
that referenced
this issue
Nov 30, 2023
Fix #678 Signed-off-by: Sagi Shnaidman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
The container is being recreated everytime the playbook runs but only if there is at least one published port which bounds to address
0.0.0.0
. Please refer to the diff output below to quickly see the problem.Steps to reproduce the issue:
Run the task shown later in this post. And then rerun it to see that the container is being recreated everytime.
Describe the results you received:
The container should only be created once instead of everytime the role task executes (see below for the task being run).
Describe the results you expected:
The container should not be recreated.
Additional information you deem important (e.g. issue happens only occasionally):
Happens nearly all the time. Only once it did not happen.
Version of the
containers.podman
collection:Either git commit if installed from git:
git show --summary
Or version from
ansible-galaxy
if installed from galaxy:ansible-galaxy collection list | grep containers.podman
Output 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
Please NOTE: if you submit a bug about idempotency, run the playbook with
--diff
option, like:ansible-playbook -i inventory --diff -vv playbook.yml
The important part of the output below is the following I think:
Full output:
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: