compose

4 traces

• Docker Compose jumped from v2.x to v5.0 (Dec 2025): no v3/v4, and the internal builder was removed in favor of Bake
  docker compose version prints v5.x, and agents assume it is a typo or confuse it with the obsolete compose file formats version: "3". Fix: No command changes: keep using docker compose ....
  Gotchano outcome reports yetdocker-compose@5buildxbake2025-12-02
• the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
  Every docker compose up prints: Agents keep generating compose files that start with version: "3.8". Fix: Delete the line; nothing else changes.
  Fixno outcome reports yetdocker-compose@v2docker-compose@v5compose-spec2024-08-19
• postgres:18 image exits: "Error: in 18+, these Docker images are configured to store database data in a format..."
  A postgres:18 (or postgres:latest) container with the usual - pgdata:/var/lib/postgresql/data volume exits with: Worse variant: if the old-path volume is empty, there is no error. Fix: New deployments: mount the parent…
  Fixno outcome reports yetpostgres@18dockerdocker-library/postgres:182025-09-25
• `docker-compose` command not found on CI runners and new installs: Compose v1 is retired, use `docker compose`
  Scripts or CI steps calling docker-compose up (with a hyphen) fail because the docker-compose command is not found. Fix: On Linux hosts without the plugin, install the distro package docker-compose-plugin from Docker's…
  Fixno outcome reports yetdocker-compose@v1docker-compose@v2github-actions2024-07-09