Command create-stack fails: building at STEP "RUN mkdir -p /etc/buildpacks": while running runtime: exit status 127

[cmoulliard]

Issue

The following command:

jam create-stack --config stack.toml --build-output build --run-output build

fails when it is executed on a Linux VM where the user is not root
and reports the following error

building at STEP "RUN mkdir -p /etc/buildpacks": while running runtime: exit status 127

Steps to Reproduce

1. Install a centos or RHEL9 vm
2. Install podman and start it

systemctl --user start podman.socket
ls $XDG_RUNTIME_DIR/podman/podman.sock

3. Git clone : https://github.com/paketo-community/ubi-base-stack
4. Install jam: v2.7.3
5. cd ubi-base-stack/stack
6. export the DOCKER_HOST export DOCKER_HOST=unix://$XDG_RUNTIME_DIR/podman/podman.sock
7. Run jam create-stack --config stack.toml --build-output build --run-output build

Versions

• jam: v2.7.3
• podman: 4.9.4-rhel

[BarDweller]

Unable to recreate...

+ cat /etc/fedora-release
Fedora release 39 (Thirty Nine)
+ podman --version
podman version 4.9.5
+ export DOCKER_HOST=unix:///run/user/1000/podman/podman.sock
+ DOCKER_HOST=unix:///run/user/1000/podman/podman.sock
+ systemctl --user start podman.socket
+ systemctl --user status podman.socket
● podman.socket - Podman API Socket
     Loaded: loaded (/usr/lib/systemd/user/podman.socket; enabled; preset: disabled)
     Active: active (listening) since Wed 2024-09-04 09:32:13 EDT; 2h 23min ago
   Triggers: ● podman.service
       Docs: man:podman-system-service(1)
     Listen: /run/user/1000/podman/podman.sock (Stream)
     CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/podman.socket

Sep 04 09:32:13 PODMANVM systemd[1033131]: Listening on podman.socket - Podman API Socket.
+ ./jam-linux-amd64 version
jam 2.9.0
+ git clone https://github.com/paketo-community/ubi-base-stack
Cloning into 'ubi-base-stack'...
remote: Enumerating objects: 758, done.
remote: Counting objects: 100% (480/480), done.
remote: Compressing objects: 100% (230/230), done.
remote: Total 758 (delta 324), reused 333 (delta 237), pack-reused 278 (from 1)
Receiving objects: 100% (758/758), 505.21 KiB | 4.11 MiB/s, done.
Resolving deltas: 100% (406/406), done.
+ cd ubi-base-stack
+ cp images.json stack
+ cd stack
+ ../../jam-linux-amd64 create-stack --config stack.toml --build-output build --run-output run
Building io.buildpacks.stacks.ubi8
  Building on linux/amd64
    Building base images
      Build complete for base images
    build: Decorating base image
      Adding CNB_* environment variables
      Adding io.buildpacks.stack.* labels
      Creating cnb user
    run: Decorating base image
      Adding io.buildpacks.stack.* labels
      Creating cnb user
      Updating /etc/os-release
    build: Updating image
    run: Updating image

  Exporting build image to build
  Exporting run image to run

[cmoulliard]

I did a new test on a RHEL9 VM using jam 2.9.0 and the error is still there. I think that permissions are different between fedora39 and RHEL ?

jam create-stack "--config ./stack/stack.toml --build-output ./stack/build/build.oci --run-output ./stack/build/run.oci"
Building io.buildpacks.stacks.ubi8
  Building on linux/amd64
    Building base images
Error: build failed:

building at STEP "RUN mkdir -p /etc/buildpacks": while running runtime: exit status 127

[cmoulliard]

FYI: We got also the same error if we build the dockerfile using podman directly

[cloud-user@rhel-9 stack]$ podman build -f build.Dockerfile .
STEP 1/5: FROM registry.access.redhat.com/ubi8/ubi-minimal:latest
STEP 2/5: USER root
--> 929b0659d190
STEP 3/5: RUN mkdir -p /etc/buildpacks
/bin/sh: error while loading shared libraries: libtinfo.so.6: cannot change memory protections
Error: building at STEP "RUN mkdir -p /etc/buildpacks": while running runtime: exit status 127

@BarDweller

[cmoulliard]

The workaround as documented here: containers/podman#3234 is to do:

sudo setenforce 0