-
-
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
podman_containers re-creating the container for each run #125
Comments
@daniel-wtd can you please paste a log run with "-vvvvv" and "--diff"? |
In containers#113 we made a change to lowercase only keys, so signals should be now upper case. Related to containers#125.
Hi @sshnaidm , thank a lot for having a look. I am also facing the SIGWINCH bug now oO. Maybe there is a difference between localhost execution and remote hosts? I will have a look today. Run on localhost:
|
In containers#113 we made a change to lowercase only keys, so signals should be now upper case. Fix tests - stop signal should be word, not number. Related to containers#125.
In containers#113 we made a change to lowercase only keys, but signals in image info are upper case. Fix tests - stop signal should be word, not number. Related to containers#125.
@daniel-wtd I fixed signals issue and released a new version with hotfix, please try to update the collection from Galaxy and try if it's OK. |
Hi, the recreation isue seems to be related to the tags: version 1 (with tag)
version 2 (without tag)
|
@daniel-wtd It's still not reproducing for me. Is it a whole playbook? Can you please try on a fresh system? |
Ha, the problem seems to be, that httpd:2 and httpd:latest are pointing to the same image. After removing httpd:latest, the play runs fine. Nevertheless, I have uploaded a paste of --diff -vvv. with httpd:latest AND httpd:2 present: https://paste.centos.org/view/06f9c48f |
OK, so for reproducing it was required to pull |
I have already done so. Thank you for investigating :) |
I think it may be good idea to check if we have the same image hash anyway, and if it's same - not to recreate. Will work on it. |
Thanks a lot for the investigation and effort. Really appreciate it. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I am running the below playbook and everytime it is running, the container will be re-created.
This also applies when recreate is set to false.
Steps to reproduce the issue:
podman ps -a
Describe the results you received:
The described container will be recreated, even if
recreate: false
Describe the results you expected:
The container should only be recreated when
recreate: true
Additional information you deem important (e.g. issue happens only occasionally):
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
):The text was updated successfully, but these errors were encountered: