Repository navigation
docs: the act rule's command runs on Ubuntu 26.04, and says what act can't show - #23
Merged
Merged
Conversation
…label option turns off
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The act rule in
docs/repo-standards.md("Checks") is split into one bullet per point and gains four things:--container-options '--security-opt label=disable', which turns off SELinux labels for that throwaway container only;Why
The rule's command stopped running.
catthehacker/ubuntu:act-latestis now Ubuntu 26.04, whosetailcan't follow/dev/nullunder the Podman machine's SELinux labels, so act's container exits at start and every job fails at its first step (3 of 3 runs). The image stays onlatest, which is also where GitHub-hostedubuntu-latestis moving (changelog).The other three sentences record limits found while measuring the rule:
ghcr.io/actions/actions-runnerlacks (bunzip2,cc,makeand others). One job passed act and then failed twice in CI on two of them. GitHub documents that image as minimal and names setup actions or a custom image as the ways to add software..gitfile points at a host path and the repository's own check fails (nektos/act#6074, closed as not planned).No issue: docs
How you checked it
scripts/check: 0.act pull_request -j test … -P ubuntu-latest=catthehacker/ubuntu:act-latest --container-options '--security-opt label=disable' --container-daemon-socket -: 0 (308 s; the job's lint, tests and leak scan all ok).podman run --entrypoint tail catthehacker/ubuntu:act-latest -f /dev/null: exits 1 alone and with five other options; keeps running with--security-opt label=disable.container:.This changes the command contributors run before pushing a workflow change.