Build fails before running build.sh with crun error: "unknown version specified"

[Syllvae]

Description

A build that previously worked now fails before build.sh is even executed.

The failure occurs during the first RUN instruction in the generated Containerfile.

Repository is based on the latest image-template.

Environment

• GitHub Actions
• Ubuntu 24.04 runner
• Runner version: 2.336.0
• Runner image: ubuntu-24.04 (20260726.254.1)

Base image:

FROM ghcr.io/ublue-os/bazzite:stable@sha256:b923f92d5a5b59eb992e269383eba2744601052da9d3d1595f76e79aa6ce2df0

The build script only:

• copies files
• enables a COPR
• swaps libfprint
• installs libfprint-2-tod1-broadcom

Nothing unusual.

Error

The image downloads successfully.

The failure happens immediately before /ctx/build.sh should execute.

[2/2] STEP 2/4:
RUN --mount=type=bind,from=ctx,source=/,target=/ctx \
    --mount=type=cache,dst=/var/cache \
    --mount=type=cache,dst=/var/log \
    --mount=type=tmpfs,dst=/tmp \
    /ctx/build.sh

error running container:
from /usr/bin/crun creating container for [/bin/sh -c /ctx/build.sh]:
unknown version specified

exit status 1

Error: building at STEP "RUN ... /ctx/build.sh":
while running runtime: exit status 1

error: recipe `build` failed with exit code 1

build.sh itself is never executed.

What I already checked

• enough disk space (about 47 GB free)
• latest image-template
• Containerfile matches the template
• build.sh contains only dnf5 package operations
• failure occurs before any dnf command is executed

Has anyone seen this recently?

Could this be related to a recent GitHub runner / Podman / Buildah / crun update?

---

Repository:

https://github.com/Syllvae/bazzite-controlvault

build.sh

Containerfile.txt

logs_82541541393.zip

[Xarianne]

EDIT: Actually the below might not have worked as the image then failed at the chunking step next (although it got past this step that has the issue). I’ll see if the underlying problem is the same but I am not at my PC to check right now.

—-Original response—-

+1. Hit the same regression on my image (also ubuntu-24.04, runner image 20260726.254.1), fails at STEP 2/5 before build.sh runs.

Workaround that unblocked me: pin the podman runtime to runc in the build recipe of the Justfile:
PODMAN_BUILD_ARGS=("${BUILD_ARGS[@]}" "${LABELS[@]}" --runtime runc --pull=newer --tag "${target_image}:${tag}" --file Containerfile)

runc is already installed on the runner alongside crun and doesn't exhibit the unknown version specified error. Build goes green after this. Happy to revert once there's an official fix in the template.

This workaround may not be needed in the future. I think the cause is a version mismatch between crun and podman introduced by the July 26 ubuntu-24.04 runner image update, not anything in this template. Once GitHub's runner image ships compatible crun/podman versions again, the default runtime should work as-is and this pin can be dropped. As I don't know how Universal Blue treats temporary workarounds I have not submitted a PR for this.

[renner0e]

looks like this issue

• [Ubuntu 24.04] podman broken on 20260726.254: uses /usr/bin/crun 1.14.1 instead of the crun 1.28 in /usr/local/bin actions/runner-images#14473

I started a fresh run on a template of mine and it seems to use:

Image: ubuntu-24.04
Version: 20260720.247.2

it seems like they rolled it back and we don't need a workaround here to me as they'll probably fix it? The window for the breakage might've been a couple hours only.

A PR that supposedly fixes it:

• [Ubuntu] Fix podman crun selection and /usr, /etc ownership broken by the podman bundle install actions/runner-images#14480

[Xarianne]

I am running a rebuild right now and it is working. Although I didn't get to the chunking step, but at least the build step did not fail even without the workaround.

[renner0e]

I am running a rebuild right now and it is working. Although I didn't get to the chunking step, but at least the build step did not fail even without the workaround.

Please link the run to the failing step.