[Solved] Build fails in some kind of permission issue

[ladd-a]

I've had to recreate my build environment and for some reason there is a permission issue at pip_install step:

[1/4] STEP 15/16: RUN /output/scripts/pip_install $PYCMD
/bin/sh: line 1: /output/scripts/pip_install: Permission denied
Error: error building at STEP "RUN /output/scripts/pip_install $PYCMD": error while running runtime: exit status 126

At first I suspected this is an issue with one of the new packages I added to the build dependencies, but removing that had no effect. Also ruled out system as it seems to happen despite disabling apparmor and trying build as root on ubuntu 22.04.

This image build fine approx. 10 months ago in similar environment (using same ubuntu version).

This is my execution-environment.yml:

---
version: 3

build_arg_defaults:
  ANSIBLE_GALAXY_CLI_COLLECTION_OPTS: '--pre'

dependencies:
  ansible_core:
    package_pip: ansible-core
  ansible_runner:
    package_pip: ansible-runner
  python:
    - jmespath
    - pyVim
    - pyVmomi
    - pexpect
    - lxml
    - pymssql
    - cryptography
    - git+https://github.com/vmware/vsphere-automation-sdk-python.git
  galaxy: galaxy.yaml

images:
  base_image:
    name: registry.redhat.io/ansible-automation-platform-24/ee-minimal-rhel9:latest

options:
  package_manager_path: /usr/bin/microdnf

$ adt --version
ansible-builder                          3.1.0
ansible-core                             2.17.4
ansible-creator                          24.9.0
ansible-dev-environment                  24.9.0
ansible-dev-tools                        24.8.0
ansible-lint                             24.9.0
ansible-navigator                        24.9.0
ansible-sign                             0.1.1
molecule                                 24.8.0
pytest-ansible                           24.9.0
tox-ansible                              24.9.0

$ python3 --version
Python 3.10.12

$ podman --version
podman version 3.4.4

Also the builder seems to run earlier python version by default, is that a problem?:

[1/4] STEP 13/16: RUN $PYCMD -V
Python 3.9.18

[Shrews]

Your EE (minus the galaxy.yaml file that was not provided) builds successfully for me on Ubuntu 22.04 using ansible-builder version 3.1 and with podman version 3.4.4.

A few questions for you:

• Are you running ansible-builder directly on your machine, or are you invoking it within a Podman container image?
• What is the exact ansible-builder command you are using for your build? Is it on the command line, or is it being invoked indirectly through the devtools utilities? If the latter, did you try running the ansible-builder command directly?
• Can you please add the -vvv option to your ansible-builder build command and provide the entire output for us to examine?

[ladd-a]

While gathering details it hit me that the context files were continuously reported up-to-date, and then I realized that I had run the initial build when files were still on a thumb-drive. I removed the context directory and everything seems to work now. This was just an user error, thanks for help.

For reference, I am running ansible-builder in QEMU KVM. I guess some limitation was set on the mounted device which caused corruption on the context directory.