Skip to content

Build Execution Environment instructions fail due to changes in the latest fedora image #2093

@2q2code

Description

@2q2code

Following instructions here:
https://docs.ansible.com/ansible/devel/getting_started_ee/build_execution_environment.html

Leads to:

# ansible-builder build --tag postgresql_ee --container-runtime docker
Running command:
  docker build -f context/Dockerfile -t postgresql_ee context
...showing last 20 lines of output...
 ---> Using cache
 ---> 2abae183e370
Step 17/72 : ARG PKGMGR
 ---> Using cache
 ---> 594932805685
Step 18/72 : COPY _build/scripts/ /output/scripts/
 ---> Using cache
 ---> 26f006b2e477
Step 19/72 : COPY _build/scripts/entrypoint /opt/builder/bin/entrypoint
 ---> Using cache
 ---> 3a2e8ef99bee
Step 20/72 : RUN /output/scripts/pip_install $PYCMD
 ---> Running in bbc361c7aadc
+ PYCMD=/usr/bin/python3
+ '[' -z /usr/bin/python3 ']'
+ '[' '!' -x /usr/bin/python3 ']'
+ echo '/usr/bin/python3 is not an executable'
+ exit 1
/usr/bin/python3 is not an executable
The command '/bin/sh -c /output/scripts/pip_install $PYCMD' returned a non-zero code: 1

An error occurred (rc=1), see output line(s) above for details.

It took me a day of messing around with this to figure out that the base image was at fault, and not my approach. I tried using pipx-installed ansible tools, and a venv using pip3. Neither worked, but they had the previous day on another machine running the same OS (arch).

Might want to lock this down to a base image version that works and not a moving target for the poor newcomer with less determination to make it work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs_triageNeeds a first human triage before being processed.new_contributorThis PR is the first contribution by a new community member.

    Type

    No type

    Projects

    Status

    ✅ Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions