Immutable solution version
Docker compose containers communication
Complete solution
[Pierre B.
[Pierre B. (accepted answer)] I understand you want to restrict communications so that containers can only communicate with other services such as: - fusionauth should be able to contact essearch, postgresdb - backend should be able to contact auth, mysql_db - auth should be able to contact fusionauth, backend - ui should be able to contact backend, auth You can use networks as you already partially do in your example to enable communication such as: - services on the same network can reach each other using the service name or alias - i.e.
Context: Stack Overflow #61244829 (accepted answer, 5 votes, 3 answers): I have 7 docker containers namely - essearch - postgresdb - fusionauth - mysqldb - auth - backend - ui The communication between containers should be like below - fusionauth should be able to contact essearch, postgresdb - backend should be able to contact auth, mysqldb - auth should be able to contact fusionauth, backend - ui should be able to contact backend, auth Existing docker-compose ``` version: '3.1' services: postgresdb: containername: postgresdb image: postgres:9.6 environment: PGDATA: /var/lib/postgresql/data/pgdata POSTGRESUSER: ${POSTGR
Evidence
Source: Stack Overflow #61244829 (accepted answer, 5 votes, 3 answers): I have 7 docker containers namely - essearch - postgresdb - fusionauth - mysqldb - auth - backend - ui The communication between containers should be like below - fusionauth should be able to contact essearch, postgresdb - backend should be able to contact auth, mysqldb - auth should be able to contact fusionauth, backend - ui should be able to contact backend, auth Existing docker-compose ``` version: '3.1' services: postgresdb: containername: postgresdb image: postgres:9.6 environment: PGDATA: /var/lib/postgresql/data/pgdata POSTGRESUSER: ${POSTGR
Verified resolution: [Pierre B. (accepted answer)] I understand you want to restrict communications so that containers can only communicate with other services such as: - fusionauth should be able to contact essearch, postgresdb - backend should be able to contact auth, mysql_db - auth should be able to contact fusionauth, backend - ui should be able to contact backend, auth You can use networks as you already partially do in your example to enable communication such as: - services on the same network can reach each other using the service name or alias - i.e.
Source URL: https://stackoverflow.com/questions/61244829
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_khnihnGD6uu_S4LUsGhsFQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Docker compose containers communication <span>— Vectle</span></a>