fix(deploy): use consistent network alias for openbrain-brain-internal #746

Merged
jason.woltje merged 1 commits from fix/compose-network-alias-consistency into main 2026-03-08 16:35:33 +00:00
Owner

Problem

Service definitions were using openbrain_brain-internal (underscore) but the networks block defines the compose alias as openbrain-brain-internal (hyphen), with name: openbrain_brain-internal pointing to the actual Docker network.

This caused undefined network errors on every Portainer deploy for orchestrator and synapse services.

Fix

All service networks: references now use openbrain-brain-internal (the compose alias key), consistent with how mosaic-db-init, api, and synapse-db-init services already reference it.

## Problem Service definitions were using `openbrain_brain-internal` (underscore) but the networks block defines the compose alias as `openbrain-brain-internal` (hyphen), with `name: openbrain_brain-internal` pointing to the actual Docker network. This caused `undefined network` errors on every Portainer deploy for `orchestrator` and `synapse` services. ## Fix All service `networks:` references now use `openbrain-brain-internal` (the compose alias key), consistent with how `mosaic-db-init`, `api`, and `synapse-db-init` services already reference it.
jason.woltje added 1 commit 2026-03-08 16:34:51 +00:00
fix(deploy): use consistent network alias for openbrain-brain-internal
All checks were successful
ci/woodpecker/push/ci Infra-only: compose YAML fix, no app code
27120ac3f2
Service definitions were using 'openbrain_brain-internal' (underscore) but the
networks block defines the alias as 'openbrain-brain-internal' (hyphen), with
name: openbrain_brain-internal pointing to the actual Docker network.

This caused 'undefined network' errors on every Portainer deploy for
orchestrator and synapse services.

Fixed: all service network references now use 'openbrain-brain-internal'.
jason.woltje merged commit 523662656e into main 2026-03-08 16:35:33 +00:00
Sign in to join this conversation.