fix: add momo-pro_default external network to scheduler for momo-db access
Some checks failed
CD Pipeline / deploy (push) Failing after 2m30s
Some checks failed
CD Pipeline / deploy (push) Failing after 2m30s
Scheduler container needs to reach momo-db (on momo-pro_default network). Without this, psycopg2 fails with DNS name resolution error on every recreate. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -241,6 +241,7 @@ services:
|
||||
- postgres
|
||||
networks:
|
||||
- momo-network
|
||||
- momo-pro_default
|
||||
logging:
|
||||
driver: "json-file"
|
||||
options:
|
||||
@@ -724,6 +725,8 @@ networks:
|
||||
momo-network:
|
||||
driver: bridge
|
||||
name: momo-network
|
||||
momo-pro_default:
|
||||
external: true
|
||||
|
||||
# =============================================================================
|
||||
# Volumes
|
||||
|
||||
Reference in New Issue
Block a user