Closed netopsengineer closed 1 month ago
Your modification of the execution-environment.yml
file to resolve the issue is the proper way of dealing with this.
Because the package manager is used within the dynamically built Containerfile
with a RUN
instruction (for example, to install the user's selected version of Python), and we do not do any sort of probing of the selected container image itself, it is required that you define the package manager within the EE file. If the assemble
script were the only place the package manager was used, we could programmatically figure out which one exists because it is run within the container.
As such, your original bug report to ansible-dev-tools
is completely valid, and I'll be closing this one.
Team,
The docs for
ansible-dev-tools
suggest creating a customexecution-environment.yml
with the following:However, this looks to create the following error during the build where
ansible-builder
is expecting to find/usr/bin/dnf
, but it appears the image is using/usr/bin/microdnf
instead:Adding the following to the
execution-environment.yml
resolves it:I originally opened an issue on
ansible-dev-tools
and was referred here https://github.com/ansible/ansible-dev-tools/issues/284 by @ssbarnea