Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Discovery from docker issue

See original GitHub issue

Now the ip.v4() get an ip of the container which is assigned by docker_gwbridge. this ip can not be accessed by any other container like colyseus proxy. So it’s may not be possible to scale in docker swarm cluster.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

endelcommented, Oct 13, 2019

This is a quote from Jorn in the Discord channel:

You can try to create a user defined bridge, it has more features than the default bridge. Or use an overlay network. It used to be done by linking containers with --link but that is deprecated Further reading: https://docs.docker.com/network/bridge/ and https://docs.docker.com/network/overlay/

Docker swarm typically uses an overlay network Kubernetes typically also uses an overlay network (though not strictly required as it has a pluggable networking model)

1reaction

ethernycommented, Oct 9, 2019

It’s not an answer to your question, but another way.

Perhapse you can use docker socket (docker.sock) to listen published labels in the swarm. Like Traefik. You can add labels to colyseus swarm instances and with a special colyseus proxy you can auto registration nodes based on published docker labels. When a new node is created it publish the IP and some other container informations, with that you can add new entries in the proxy.

https://medium.com/better-programming/about-var-run-docker-sock-3bfd276e12fd