act
Overview
Version & Lifecycle
Community Notes
act Docker prerequisite, runner image, and per-run input file note
For managed act installs, remember that act is not a standalone GitHub Actions runner: the project README says it uses the Docker API to pull or build the container images that workflow jobs need. Make Docker Desktop or another reachable Docker Engine part of the prerequisite check before treating act failures as package-install failures.
Keep runner-image and host-architecture choices explicit in repeatable scripts. The act command source documents -P/--platform for mapping workflow labels such as ubuntu images to a specific container image, --container-architecture linux/amd64 for architecture control, and --container-daemon-socket when the Docker socket should be selected or not bind-mounted.
Do not bake secrets into the install package or into a shared desktop profile. The CLI supports per-run files for --secret-file, --var-file, --env-file, and --input-file; its config-file lookup also reads act/actrc under the user config path plus .actrc in the home and invocation directories, so deployment defaults can be different from per-repository test inputs.
Sources: nektos/act README and act command-line option definitions.
Release Notes & Updates
Help us match vulnerabilities
No vulnerability match yet. Pick the right product:
Don’t see it? Paste a CPE
Also known as
Other names people use for this app — helps search and matching.
Sign in to suggest a name.
Packaging Notes
Uses Docker images to simulate GitHub Actions environments locally
