simple container builds fail w/ unified hierarchy

[mrguitar]

The message below makes me think this is an issue between cgroups & runc. I'm not sure if this is the cause or symptomatic of something else.

STEP 1: FROM registry.access.redhat.com/ubi8
STEP 2: ADD --chown=1000:1000 ocp4 /ocp4
c9cd957f1685bbc1addeb9a8296ee140bc3ff14f116f09f793d95e4d5b658745
STEP 3: RUN yum install -y openssh-clients sudo; yum -y clean all
WARN[0000] signal: killed
ERRO[0000] container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused "mountpoint for cgroup not found""
container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused "mountpoint for cgroup not found""
error running container: error creating container for [/bin/sh -c yum install -y openssh-clients sudo; yum -y clean all]: : exit status 1
Error: error building at STEP "RUN yum install -y openssh-clients sudo; yum -y clean all": error while running runtime: exit status 1

[giuseppe]

from the log it seems like runc is used instead of crun (there is no process_linux.go file in libpod). What version of Podman are you using? Could you pleaes confirm that Podman/Buildah are configured to use crun?

[mrguitar]

yup that's it. Thank you. If I pass --runtime= to crun it works perfectly. I think this points to a podman bug though. I have the runtime defined in libpod.conf but it's not using crun w/ podman build. Thanks again.

[giuseppe]

I've opened a PR to fix the issue in Podman: containers/podman#3785

[giuseppe]

closing the issue as it was fixed in Podman