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
podman_container always recreates the container #31
Labels
Comments
sshnaidm
added
bug
Something isn't working
bug/idempotency
Bug related to idempotency of modules
labels
May 5, 2020
Got the same issue when trying to recreate a container in a pod. Using podman version 1.6.4 in CentOS 7.
|
@sshnaidm Saw your fix for cgroup_parent. It works!
|
This was referenced May 10, 2020
@falstaff1288 this happens because container was in a pod, #40 should help |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
containers.podman.podman_container
always recreates the container, becausestop_signal
andvolume
properties differ.Steps to reproduce the issue:
Run it
Run it again
Describe the results you received:
Using
-D
one can see that it recreates the container:Describe the results you expected:
The container should have been
OK
and notchanged
.Additional information you deem important (e.g. issue happens only occasionally):
One could add an additional parameter like comparisions to fix this.
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
):See above
Command line and output of ansible run with high verbosity:
Additional environment details (AWS, VirtualBox, physical, etc.): AWS
The text was updated successfully, but these errors were encountered: