When building an execution environment with a centos10-minimal base image, how do you configure containerfile PKGMGR to be microdnf instead of dnf?
It looks like context/_build/scripts/assemble will correctly discover and use microdnf, but before (?) then, the containerfile is built with hard coded dnf. Can this be overridden?
$ ansible-builder build -vvv
[...]
Running command:
podman build -f context/Containerfile -t ansible-execution-env:latest context
[...]
[1/3] STEP 13/14: RUN $PKGMGR install $PYPKG -y ; if [ -z $PKGMGR_PRESERVE_CACHE ]; then $PKGMGR clean all; fi
/bin/sh: line 1: /usr/bin/dnf: No such file or directory
$ ansible-builder build -vvv
jsonschema.exceptions.ValidationError: Additional properties are not allowed ('options' was unexpected)
Failed validating 'additionalProperties' in schema['properties']['images']:
{'additionalProperties': False,
'properties': {'base_image': {'properties': {'name': {'type': 'string'},
'signature_original_name': {'type': 'string'}},
'type': 'object'}},
'type': 'object'}
On instance['images']:
{'base_image': {'name': 'quay.io/centos/centos:stream10-minimal'},
'options': {'package_manager_path': '/usr/bin/microdnf'}}
The above exception was the direct cause of the following exception:
ansible_builder.exceptions.DefinitionError: Additional properties are not allowed ('options' was unexpected)