Skip to content

[BUG] Docker Compose setup fails on main branch due to config–image mismatch #9320

@Shailesh-714

Description

@Shailesh-714

In docker-compose.yml, critical services including:

  • hyperswitch-server
  • migration_runner
  • hyperswitch-producer
  • hyperswitch-consumer
  • hyperswitch-drainer

use standalone images from the stable release (standalone tag) but mount local config files from the current branch:

volumes:
  - ./config:/local/config

This creates a mismatch between stable images and branch-local configs. As a result:

  1. On branches ahead of latest (e.g., main), configs may include values not yet supported by the stable images
  2. Critical services can fail to start (hyperswitch-server, migration_runner, schedulers, drainer)
  3. Users are unable to reliably run the stack using docker-compose.yml

This directly impacts the user experience, as the documented Compose setup fails outside the latest branch.

Solution

Update docker-compose.yml so that it always uses config files from the latest branch (stable release) instead of local configs.

docker-compose-development.yml will continue to exist for local development where branch-local configs are needed.

Benefits of this change:

  1. Ensures docker-compose.yml works reliably on any branch
  2. Prevents config–image mismatches that break critical services
  3. Provides users with a stable setup experience
  4. Keeps a clear separation between stable (docker-compose.yml) and development (docker-compose-development.yml) use cases

Files to modify

  • docker-compose.yml

Verification Steps

  1. On the latest branch:

    • Run docker compose up
    • Verify all critical services (hyperswitch-server, migration_runner, producer, consumer, drainer) start successfully
  2. On the main branch (ahead of latest):

    • Run docker compose up
    • Confirm services still start correctly, since configs are fetched from latest

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomershacktoberfestIssues that are up for grabs for Hacktoberfest participants

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions