Skip to content

docs: the act rule's command runs on Ubuntu 26.04, and says what act can't show - #23

Merged
thatsrue merged 2 commits into
mainfrom
docs/act-rule-latest
Nov 19, 2026
Merged

thatsrue merged 2 commits into
mainfrom
docs/act-rule-latest

Conversation

@thatsrue

@thatsrue thatsrue commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

What changed

The act rule in docs/repo-standards.md ("Checks") is split into one bullet per point and gains four things:

  • the command passes --container-options '--security-opt label=disable', which turns off SELinux labels for that throwaway container only;
  • act runs from a plain clone, not a linked worktree;
  • a green act run doesn't show that a tool exists on the ARC runner image: a step installs what it calls or uses a setup action;
  • a test that fails only on Linux isn't caught before the push; CI is the gate for that.

Why

The rule's command stopped running. catthehacker/ubuntu:act-latest is now Ubuntu 26.04, whose tail can't follow /dev/null under 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 on latest, which is also where GitHub-hosted ubuntu-latest is moving (changelog).

The other three sentences record limits found while measuring the rule:

  • act's image holds 14 of 60 checked tools that ghcr.io/actions/actions-runner lacks (bunzip2, cc, make and 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.
  • From a linked worktree the copied .git file points at a host path and the repository's own check fails (nektos/act#6074, closed as not planned).
  • Three red runs in one week were tests that pass on macOS and fail on Linux (a macOS-only API, a case-variant path, a process-list check). The rule only runs on workflow changes and doesn't cover them. This is a known gap, not built against: none since, and a Linux run of every check before every push would double the local gate.

No issue: docs

How you checked it

  • scripts/check: 0.
  • The documented command, from a plain clone of a repository whose CI is green: 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).
  • The same command without the option: 1, "can only create exec sessions on running containers".
  • 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.
  • Both new links return 200, and the GitHub page carries the "least amount of packages" sentence.
  • Not run: the option on a job with container:.

This changes the command contributors run before pushing a workflow change.

  • A bug fix comes with a test that fails without it
  • Docs match how it works now
  • No secrets or private information

@thatsrue thatsrue added the documentation Improvements or additions to documentation label Nov 19, 2026
@thatsrue thatsrue changed the title docs: the act rule runs on the latest image again, and says what act can't show docs: the act rule's command runs on Ubuntu 26.04, and says what act can't show Nov 19, 2026
@thatsrue
thatsrue merged commit f2d1d3b into main Nov 19, 2026
1 check passed
@thatsrue
thatsrue deleted the docs/act-rule-latest branch November 19, 2026 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Development

Successfully merging this pull request may close these issues.

1 participant