The job container had no way to reach the docker-dind sidecar, so
'docker compose' failed with 'no such file or directory' on the unix
socket. Set DOCKER_HOST to the dind TCP endpoint and share the pod's
network namespace so the container can reach localhost:2375.
The docker.io apt package doesn't ship the compose plugin, and the
npm docker-compose package is an unrelated legacy tool that doesn't
provide the 'docker compose' CLI subcommand. Install the official
compose v2 binary as a docker CLI plugin instead.
act_runner does not automatically read the mounted docker config for
image pulls; credentials must be supplied explicitly per job via the
container.credentials field.
Switch all jobs to run inside git.byting-pandas.ninja/ci/node22-docker,
which bundles Node 22, Docker CLI, and docker-compose. Removes the
actions/setup-node step since Node is already provided by the image.
Base image for the gitea-act-runner build environment, includes
Docker CLI and docker-compose for CI jobs that need to build/push
containers, plus corepack for yarn/pnpm support."
- Changed push branch filter to wildcard '*' to test feature branches before merging
- Kept the missing pnpm/node setup fix for the component-tests job
- Changed push branch filter to wildcard '*' to test feature branches before merging
- Kept the missing pnpm/node setup fix for the component-tests job
Every job runs in an isolated container. The component-tests job
was missing the Node.js and pnpm installation steps, causing
command not found errors (exit code 127) during local execution.
Adds automated checks that were previously only run manually and
locally, closing the last remaining gap before dev can be merged
into main with confidence.
Runs on every push and pull request targeting dev or main:
- lint (eslint)
- format check (prettier --check)
- changeset presence check (non-blocking for now, see comment in
workflow file)
- unit tests (vitest)
- component/browser tests (vitest + playwright, via the existing
Docker test setup)
Fixes: #10
Ninosaurier