Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to build EE #722

Open
adn1107 opened this issue Jan 23, 2025 · 3 comments
Open

Not able to build EE #722

adn1107 opened this issue Jan 23, 2025 · 3 comments
Labels
needs_info Waiting on feedback. Will be closed.

Comments

@adn1107
Copy link

adn1107 commented Jan 23, 2025

my execution-environment.yml:

---
version: 3

# ansible_config: ansible.cfg

dependencies:
  # ansible_core:
  #   package_pip: ansible-core==2.14
  galaxy: requirements.yml
  python: requirements.txt

images:
  base_image:
    # name: registry.redhat.io/ansible-automation-platform-22/ee-supported-rhel8:latest
    name: registry.redhat.io/ansible-automation-platform-24/ee-minimal-rhel8:latest

options:
  package_manager_path: /usr/bin/microdnf

additional_build_files:
  - src: files/ansible.cfg # copy contents from files to configs dir in build context
    dest: configs

# additional_build_steps:
#   append_final:
    # reference the file from build context like this
    # - COPY _build/configs/ansible.cfg /etc/ansible/ansible.cfg
    # - ADD _build/configs/ansible.cfg /etc/ansible/ansible.cfg


      #additional_build_steps:
      #prepend_base: 
      #- RUN pip3 install --upgrade pip setuptools 
      #- RUN pip3 install jmespath
      #append_final:
      #- RUN ls -la /etc
~                                                                                                                                         
~                                                                                                                                         
~                                                                                                                                         
~                                             

Error:

Running command:
  podman build -f context/Containerfile -t ansiblezosforconcert context
[1/4] STEP 1/11: FROM registry.redhat.io/ansible-automation-platform-24/ee-minimal-rhel8:latest AS base
[1/4] STEP 2/11: USER root
--> 6a8756961c09
[1/4] STEP 3/11: ARG EE_BASE_IMAGE
--> ab179618f5b7
[1/4] STEP 4/11: ARG PYCMD
--> 305236951cd0
[1/4] STEP 5/11: ARG PKGMGR_PRESERVE_CACHE
--> c52bec9ccfe0
[1/4] STEP 6/11: ARG ANSIBLE_GALAXY_CLI_COLLECTION_OPTS
--> 4b22519ebd7b
[1/4] STEP 7/11: ARG ANSIBLE_GALAXY_CLI_ROLE_OPTS
--> ec47abb24a3e
[1/4] STEP 8/11: ARG PKGMGR
--> 5daa521f0a3c
[1/4] STEP 9/11: RUN $PYCMD -m ensurepip
error running container: from /usr/bin/crun creating container for [/bin/sh -c $PYCMD -m ensurepip]: unknown version specified
: exit status 1
time="2025-01-23T15:17:02-08:00" level=error msg="did not get container create message from subprocess: EOF"
Error: building at STEP "RUN $PYCMD -m ensurepip": while running runtime: exit status 1
@github-actions github-actions bot added the needs_triage New item that needs to be triaged label Jan 23, 2025
@Shrews
Copy link
Contributor

Shrews commented Jan 24, 2025

It helps us greatly when you supply the ansible-builder command you are using, and relevant environment and version information, such as:

  • host operation system and version
  • Python version
  • ansible-builder version
  • podman version

Please supply this information.

It looks like you are using ansible-builder version 3.0 based on the output, but I am unable to reproduce your error with the EE file you supplied. I also tried with the latest ansible-builder version 3.1 and had no issues.

This looks like it may be an issue with your environment, possibly with your version of podman. I tried this with podman versions 4.9.3 and 5.3.1. If your version is older, perhaps try upgrading, or maybe try building on a different host.

@Shrews Shrews added needs_info Waiting on feedback. Will be closed. and removed needs_triage New item that needs to be triaged labels Jan 24, 2025
@adn1107
Copy link
Author

adn1107 commented Jan 24, 2025

Last login: Thu Jan 23 15:02:02 2025 from 9.55.152.119
[root@hcfhub1 ~]# podman --version
podman version 5.2.2
[root@hcfhub1 ~]# uname
Linux
[root@hcfhub1 ~]# uname -a
Linux hcfhub1.fyre.ibm.com 5.14.0-284.30.1.el9_2.s390x #1 SMP Fri Aug 25 09:26:01 EDT 2023 s390x s390x s390x GNU/Linux
[root@hcfhub1 ~]# python --version
Python 3.9.21
[root@hcfhub1 ~]# ansible-builder --version
3.0.0

@Shrews
Copy link
Contributor

Shrews commented Jan 24, 2025

Thanks for that info.

I'm not a podman expert, but your build seems to be using crun for the OCI runtime, whereas mine is using runc. What is the output of this command?

/usr/bin/crun --version

If you uninstall crun, does it affect the run of ansible-builder?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_info Waiting on feedback. Will be closed.
Projects
None yet
Development

No branches or pull requests

2 participants