-
-
Notifications
You must be signed in to change notification settings - Fork 148
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 quadlet downloads image in checkrun #876
Comments
Should be fixed by #872 in 1.16.2, please check your collection version |
Thanks for the answer @sshnaidm Just out of curiosity I tested the same without |
@mstinsky when you need to run the container it has to download the image of course, how would you run it otherwise? |
In a checkrun the system should not be changed at all and I would count downloading a container image into that. |
What do you mean by "checkrun"? The check mode? If so, then yeah, we don't need to download it then. |
On the other hand when we compare images we must have it downloaded, Podman doesn't know to inspect images in registry, and having Skopeo as a requirement I think it's an overkill. So either we don't download and then don't have an exact comparison, or we do download in check mode and have exact results about changes in the container. |
As the title stats.
When using podman_container with state quadlet and running in check mode the module downloads the image defined in the ansible task.
A checkrun should not do that and only show the quadlet file that is rendered.
Simple test:
Before running the task check podman images that shows the image does not exist.
Running the task in check mode shows:
/etc/containers/systemd
does not have the quadlet file as expected but the image was downloaded:The text was updated successfully, but these errors were encountered: