Files
app/docker/compose.ci.yml
stroblmeandClaude Opus 5 c33fa404a4
Docs / docs (push) Successful in 21s
Playwright Tests / test-playwright (1, 2) (push) Failing after 2m4s
Playwright Tests / test-playwright (2, 2) (push) Failing after 1m36s
pre-commit / pre-commit (push) Successful in 3m0s
Test Backend / test-backend (push) Successful in 2m6s
Compose Smoke Test / test-compose (push) Successful in 30s
Playwright Tests / merge-reports (push) Failing after 1m2s
Keep the dev bind mounts out of CI, where they land nowhere
compose.dev.yml mounts the source over the image's own copy so `--reload`
means something in a detached local stack, and mounts the Playwright report
out to the host. Under act_runner the daemon is a sibling of the job rather
than its host: it resolves those paths against its own filesystem, finds
nothing, and mounts empty directories. So the backend reported "Path does not
exist fluksio/main.py" for a file the image plainly ships, and every shard
uploaded nothing — "No files were found with the provided path:
frontend/blob-report".

compose.ci.yml now puts backend's volumes back to what compose.yml declares
and drops Playwright's entirely; the shard copies its report out of the
container before the teardown instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-24 21:42:04 +02:00

73 lines
2.9 KiB
YAML

# CI isolation overrides — layered on top of compose.yml + compose.dev.yml by
# the Playwright shards and the compose smoke job in .gitea/workflows/.
#
# A self-hosted runner can put several jobs on the same host. A per-job
# COMPOSE_PROJECT_NAME keeps their containers, networks and volumes apart, but
# it does not cover the two things that are global to the Docker daemon:
#
# 1. `container_name` ignores the project name, so a second job fails with
# "the container name /fluksio-db is already in use".
# 2. Published host ports are first come, first served.
#
# Neither is needed in CI: everything reaches everything else by compose
# service name on the project network.
services:
proxy:
ports: !reset []
db:
container_name: !reset null
redis:
container_name: !reset null
adminer:
container_name: !reset null
ports: !reset []
mailcatcher:
ports: !reset []
backend:
container_name: !reset null
ports: !reset []
# compose.dev.yml mounts the source over the image's own copy, so `--reload`
# means something in a detached local stack. Here the daemon is a sibling of
# the job rather than its host: it resolves that path against its own
# filesystem, finds nothing, and mounts an empty directory over the package.
# That is how the container came to report "Path does not exist
# fluksio/main.py" for a file the image plainly ships. Back to what
# compose.yml declares — CI wants the built image anyway.
volumes: !override
- app-flow-data:/data
frontend:
container_name: !reset null
ports: !reset []
# Baked at build time. compose.dev.yml bakes http://localhost:8000, which
# resolves to the playwright container itself; the browser has to reach the
# API by service name on the project network instead.
build:
args:
- VITE_API_URL=http://backend:8000
# Image tags are daemon-global too, and this one no longer holds the same
# bytes as the smoke job's: without a per-job tag the two jobs overwrite
# each other's `fluksio-frontend:latest` and the SPA calls the wrong API.
image: '${DOCKER_IMAGE_FRONTEND?Variable not set}:${COMPOSE_PROJECT_NAME:-ci}'
playwright:
ports: !reset []
# Same reason as backend above. These two exist so a local run leaves its
# report on the host; under a sibling daemon they are empty directories the
# report is written into and never seen again, which is what "No files were
# found with the provided path: frontend/blob-report" was. The job copies
# the report out of the container instead.
volumes: !reset []
# frontend/playwright.config.ts defaults baseURL to http://app.localhost,
# which is right for a local run against the integrated stack but resolves
# to 127.0.0.1 in here. In CI the nginx `frontend` service serves the SPA.
# This origin must stay in BACKEND_CORS_ORIGINS (.env.example).
environment:
- PLAYWRIGHT_BASE_URL=http://frontend