Error: buildah exited with code 1 Trying to pull registry.access.redhat.com/ubi8/ubi:latest... Getting image source signatures Copying blob sha256:c7965aa7086045a59bdb113a1fb8a19d7ccf7af4133e59af8ecefd39cda8e0b1 Copying blob sha256:c7965aa7086045a59bdb113a1fb8a19d7ccf7af4133e59af8ecefd39cda8e0b1 Copying config sha256:7b13db19b1f3b9fc14a6bae2c709a5039715c01d0d705136e04dee472234a321 Writing manifest to image destination Storing signatures WARNING: Running pip install with root privileges is generally not a good idea. Try `pip install --user` instead. WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. ERROR: Could not open requirements file: [Errno 2] No such file or directory: '/usr/share/ansible/collections/ansible_collections/azure/azcollection/requirements-azure.txt' error building at STEP "RUN ansible-galaxy role install -r /tmp/requirements.yml --roles-path "/usr/share/ansible/roles" && ansible-galaxy collection install -vv -r /tmp/requirements.yml --collections-path "/usr/share/ansible/collections" && pip install --no-cache-dir -r /usr/share/ansible/collections/ansible_collections/azure/azcollection/requirements-azure.txt && pip install --no-cache-dir -r /usr/share/ansible/collections/ansible_collections/community/vmware/requirements.txt && pip install --no-cache-dir -r /usr/share/ansible/collections/ansible_collections/google/cloud/requirements.txt && pip install --no-cache-dir -r /usr/share/ansible/collections/ansible_collections/kubernetes/core/requirements.txt": error while running runtime: exit status 1 time="2024-06-27T08:48:31Z" level=error msg="exit status 1"

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.