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.
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.