Repository navigation
Missing network information in Docker Compose #543
Description
When using concore build --type docker --compose, the generated docker-compose.yml does not include a shared Docker network definition. This will make all the = ZMQ-based nodes fail when trying to connect to each other across containers, because each container resolves localhost as itself rather than the peer node.
From the perspective of ZMQ integration, the current compose generation is logically incomplete. ZMQ-based nodes rely on TCP sockets to stablish direct peer-to-peer connections. However, inside a Docker container, localhost resolves to the container's own isolated loopback interface not the host, and not the peer containers.
The graph's edges (ZMQ ports) are completely severed.
Activity
GREENRAT-K405 commentedon Apr 12, 2026
@pradeeban please have a look, I think this needs a fix!
pradeeban commentedon Apr 12, 2026
@GREENRAT-K405 sure, go ahead.
GREENRAT-K405 commentedon Apr 14, 2026
@pradeeban ,during fixing this issue, I have also discovered that the Docker compose suffered from compounding issues regarding race conditions, undocumented named volumes, and missing build contexts.
pradeeban commentedon Apr 14, 2026
Interesting!
GREENRAT-K405 commentedon Apr 14, 2026
I will raise a PR soon with the best possible solution as of right now, but I believe we will be working on this part a lot as the specification for deps of the different nodes get more clear during the actual coding period!
pradeeban commentedon Apr 14, 2026
Yes, a lot of this is meant to be fixed during the GSoC coding period.