marcel/familienarchiv
1
0
Fork 0
Code Issues 125 Pull Requests Actions Packages Projects Releases Wiki Activity

fix: replace docker-compose v1 with docker compose v2 in e2e workflow #3

New Issue
Closed
opened 2026-03-17 19:54:47 +01:00 by marcel · 0 comments
marcel commented 2026-03-17 19:54:47 +01:00
Owner
Copy Link

Problem

The e2e CI job fails immediately with:

/var/run/act/workflow/1: line 2: docker-compose: command not found
exitcode '127': command not found

Root cause: The workflow uses docker-compose (v1, standalone binary) on lines 67 and 72 of .gitea/workflows/ci.yml. Modern Docker installations (Docker Engine 20.10+) ship Compose as a plugin (docker compose, with a space), and the v1 standalone binary is not installed on the act runner.

Fix

Replace the two occurrences in .gitea/workflows/ci.yml:

- docker-compose up -d db minio create-buckets
+ docker compose up -d db minio create-buckets

- until docker-compose exec -T db pg_isready -U archive_user; do sleep 2; done
+ until docker compose exec -T db pg_isready -U archive_user; do sleep 2; done

No other changes needed — docker compose v2 is a drop-in replacement for all flags used here.

## Problem The e2e CI job fails immediately with: ``` /var/run/act/workflow/1: line 2: docker-compose: command not found exitcode '127': command not found ``` **Root cause:** The workflow uses `docker-compose` (v1, standalone binary) on lines 67 and 72 of `.gitea/workflows/ci.yml`. Modern Docker installations (Docker Engine 20.10+) ship Compose as a plugin (`docker compose`, with a space), and the v1 standalone binary is not installed on the act runner. ## Fix Replace the two occurrences in `.gitea/workflows/ci.yml`: ```diff - docker-compose up -d db minio create-buckets + docker compose up -d db minio create-buckets - until docker-compose exec -T db pg_isready -U archive_user; do sleep 2; done + until docker compose exec -T db pg_isready -U archive_user; do sleep 2; done ``` No other changes needed — `docker compose` v2 is a drop-in replacement for all flags used here.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0-critical
Blocks a core user journey, causes data loss, or is a security/accessibility barrier. Work on this before P1+.
 P1-high
Significant friction on a main user journey; workaround exists but is non-obvious. Next up after P0.
 P2-medium
Noticeable improvement; doesn't block anything; schedule opportunistically.
 P3-later
Cosmetic or parking-lot work; fine to stay open indefinitely.
 audit
Read-only audit / assessment work; produces a report rather than changing code
 bug
Something isn't working
 cleanup
Removal of dead code, vague comments, naming violations, and scratch artifacts
 collaboration
We want to extend the family archive to have more collaboration tools
 conversation
descoped
We will do that later
 devops
documentation
README, ARCHITECTURE, GLOSSARY, CONTRIBUTING, per-domain docs
 epic
Marker for epic-level issues that group multiple child issues
 feature
file-upload
legibility
Codebase Legibility Refactor — preparing the codebase for human evaluation and bus-factor reduction
 notification
person
phase-1: security
Security hygiene — must be done first
 phase-2: container-images
Production-ready multi-stage Docker images
 phase-3: prod-compose
Production compose overlay + Caddy reverse proxy
 phase-4: spring-prod-profile
Spring Boot production configuration profile
 phase-5: backups
Database and object storage backup strategy
 phase-6: deployment-docs
.env.example, DEPLOYMENT.md, runbook
 phase-7: monitoring
Prometheus, Loki, Grafana, Alertmanager
 refactor
Code restructuring without behaviour change
 security
test
ui
UI/UX and accessibility issues
 user
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Jens marcel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marcel/familienarchiv#3
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?