Later pushing as needed podman manifest push ee-test
Some questions come to mind:
1) Can it be assumed the resulting images are configured in the same manner they would be had ansible-builder build been used instead? (Are there any reasons to not do the above when a multi-arch is needed?)
2) Is there an opportunity here for the user to provide an alternative to the built-in "build" command https://github.com/ansible/ansible-builder/blob/devel/src/ansible_builder/main.py#L189 If supported in the execution-environment.yml file it could be used later or shared to rebuild in the same manner if needed. (the tag and manifest keywords would need to be account for) If supplied as podman/docker specific this could acount for buildx.
3) (if not) Can we document the above approach in a FAQ or examples section of the docs? What would be the best place? (happy to PR)
thank again for all the builder work, everytime I use it I reappreciate how handy it is.
Using a simple starting point:
multi-arch can be accomplished with:
Later pushing as needed
podman manifest push ee-test
Some questions come to mind:
1) Can it be assumed the resulting images are configured in the same manner they would be had
ansible-builder build
been used instead? (Are there any reasons to not do the above when a multi-arch is needed?) 2) Is there an opportunity here for the user to provide an alternative to the built-in "build" command https://github.com/ansible/ansible-builder/blob/devel/src/ansible_builder/main.py#L189 If supported in theexecution-environment.yml
file it could be used later or shared to rebuild in the same manner if needed. (the tag and manifest keywords would need to be account for) If supplied as podman/docker specific this could acount for buildx. 3) (if not) Can we document the above approach in a FAQ or examples section of the docs? What would be the best place? (happy to PR)thank again for all the builder work, everytime I use it I reappreciate how handy it is.
-brad