Is there a status or suggested workaround for this?
We are using multiple networks to work around the lack of `network_mode: “service:service_name”``
One container is on two networks (a custom network, and the default network)
We have to specify the default network in addition to our custom network, otherwise the container will not be on the default network. Since only the network name is supported in balena docker compose, the container does not get its regular alias (the service name) on the default network.
This is pretty significant blocker, as it means we cannot route to a container by the service name (or any alias) if it is on more than one network.