You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
podman build has a --pull option that sets pull policy for the base image when building a new image. By default, this is missing.
There appears to be no way to set or override this pull policy in ansible-builder. This means that if you have a base image of tag :latest, it will never be updated by builder after the initial pull.
Is there any way to get ansible-builder to update the base image when it runs? If not, I think a --pull option would be a useful addition to builder. This could be upgraded to --pull-always if container policy requires it, e.g. with signature_required.
I don't want to do a separate podman pull of the image beforehand, because that means I have to repeat the base image name in the schema and in the podman pull.
The text was updated successfully, but these errors were encountered:
As a workaround, you can create context directory including Dockerfile by ansible-builder create command first, then build the context by podman build command with --pull=always.
podman build
has a--pull
option that sets pull policy for the base image when building a new image. By default, this ismissing
.There appears to be no way to set or override this pull policy in ansible-builder. This means that if you have a base image of tag
:latest
, it will never be updated by builder after the initial pull.Is there any way to get ansible-builder to update the base image when it runs? If not, I think a
--pull
option would be a useful addition to builder. This could be upgraded to--pull-always
if container policy requires it, e.g. withsignature_required
.I don't want to do a separate
podman pull
of the image beforehand, because that means I have to repeat the base image name in the schema and in thepodman pull
.The text was updated successfully, but these errors were encountered: