Discovery from docker issue
See original GitHub issueNow 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 Results From Across the Web
Network Discovery causes hang of Docker container #4774
I'm not able to reproduce the problem, I'm currently running ntopng version: 4.2.201105 and after running Network Discovery the system seems ...
Read more >Docker discovery isn't working. - Support and Troubleshooting
Docker discovery is not working. Release J and above. Cause This could happen if the Docker pattern wasn't triggered at all. Check that...
Read more >Docker Plugin API
Plugin discovery . Docker discovers plugins by looking for them in the plugin directory whenever a user or container tries to use one...
Read more >Docker Swarm Service Discovery | Problem in Implementation
I got the problem which i was facing, actually when we change the permissions to read-write for docker.sock, permissions are only changed till ......
Read more >Docker compose com.netflix.discovery.shared.transport ...
I have a problem in docker-compose file. Eureka server and api gateways throws an issue defined below while there is no issue in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is a quote from Jorn in the Discord channel:
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