-
-
Notifications
You must be signed in to change notification settings - Fork 138
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_image
don't rebuilt the image if I set a new containerfile
#646
Comments
I think it's impossible to know if it's a different Containerfile or same Containerfile with different content, or just same. So it's better to force building if any Containerfile is set. You can use |
Yes. I have inspected an image created by Maybe we can add a new parameter to So, next time we run |
That's an interesting idea! I think we can use "annotations" for that? It's exactly for image metadata info. |
I would like to. 😃 But for now I don't have enough time because of school. |
@CyberFox001 are you still interested to create a patch or can I take it? |
@sshnaidm Sadly, I'm working on my diploma work right now. And I will be very busy until end of September. You are free to take it. |
/kind bug
Description
If I:
podman_image
, in a playbook, to built an image from a ContainerfileThe image is not built again.
But the requested image is different because the Containerfile is different. So the image should be rebuild in this case.
Steps to reproduce the issue:
Create a playbook and use
podman_image
withstate
tobuild
andbuild.file
to a ContainerfileRun the playbook
Modify the playbook to set
podman_image.build.file
to another ContainerfileRun the playbook again
Describe the results you received:
The image is not build again.
Describe the results you expected:
The image should be build again.
Version of the
containers.podman
collection:Output of
ansible --version
:Output of
podman version
:Package info (e.g. output of
rpm -q podman
orapt list podman
):The text was updated successfully, but these errors were encountered: