Docker compose containers communication
Shows how to fix docker compose containers communication. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
[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.
Steps
- [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.
When to use
Use this skill when you run into "Docker compose containers communication".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.