Skip to content

podman: run the current podman from the distrobox AppImage - #170

Open
Nemo-010 wants to merge 1 commit into
blue-build:mainfrom
Nemo-010:podman-from-appimage
Open

Nemo-010 wants to merge 1 commit into
blue-build:mainfrom
Nemo-010:podman-from-appimage

Conversation

@Nemo-010

@Nemo-010 Nemo-010 commented Nov 7, 2026

Copy link
Copy Markdown

greetings from Port Edwards.

The runner images do not ship a podman this action can use: 22.04 has none at
all, and the others are behind. The distrobox AppImage builds podman from
current sources and is multi-call: named podman, it runs its bundled podman
together with conmon and crun, so every runner gets the same current podman
instead of a different one per image.

It goes into ~/bin with its portable folders (podman.home, .share, .cache,
.config), so podman keeps its state next to the AppImage. That also keeps it
away from the BoltDB database an older podman leaves in
~/.local/share/containers, which podman 6 refuses to start with. From 24.04 on
the unprivileged_userns AppArmor profile only lets a binary with its own
profile create a rootless user namespace, so the step loads one for that path.

The step now runs after the cosign installer: that one puts /usr/bin on
$GITHUB_PATH, and the runner prepends the last entry written, so a step before
it would leave the runner's own podman first in PATH.

Determine Vars also drops --variable and --expand-header for a plain -H: those
need curl 8.3 and the 22.04 image has 7.81, which made the action fail there
before it ever reached podman.

Tested with squash on ubuntu-22.04, ubuntu-24.04 and ubuntu-latest: podman
6.1.4 from the AppImage in PATH, image built and pushed on all three.


Requested by fiftydinar via errand.
Conversation: https://discord.com/channels/1313385177703256064/1567916538919395398

greetings from Port Edwards.

The runner images do not ship a podman this action can use: 22.04 has none at
all, and the others are behind. The distrobox AppImage builds podman from
current sources and is multi-call: named podman, it runs its bundled podman
together with conmon and crun, so every runner gets the same current podman
instead of a different one per image.

It goes into ~/bin with its portable folders (podman.home, .share, .cache,
.config), so podman keeps its state next to the AppImage. That also keeps it
away from the BoltDB database an older podman leaves in
~/.local/share/containers, which podman 6 refuses to start with. From 24.04 on
the unprivileged_userns AppArmor profile only lets a binary with its own
profile create a rootless user namespace, so the step loads one for that path.

The step now runs after the cosign installer: that one puts /usr/bin on
$GITHUB_PATH, and the runner prepends the last entry written, so a step before
it would leave the runner's own podman first in PATH.

Determine Vars also drops --variable and --expand-header for a plain -H: those
need curl 8.3 and the 22.04 image has 7.81, which made the action fail there
before it ever reached podman.

Tested with squash on ubuntu-22.04, ubuntu-24.04 and ubuntu-latest: podman
6.1.4 from the AppImage in PATH, the AppArmor profile loaded where the
restriction exists, and the image built and pushed on all three.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant