Closed BrianAdams closed 8 years ago
Hopefully obvious, but the Gorp service when queried on a normally working instance is:
{ "options": { "host": "", "port": 8000, "protocol": "tcp", "method": "wrr", "persistent": false }, "health": 1, "backends": [ "motd_8000_tcp" ] }
Where the variance is in the backends
Looks like this may be similar to the last naming issue. When the services are listed from the swarm event stream they have an additional data element which is the host they are running on.
Swarm Stream:
dockhero-motd-http_8000_tcp/swarm-node-1/motd_8000_tcp]
Host Stream:
dockhero-motd-http_8000_tcp/motd_8000_tcp
Accessing the service on the load balanced port fails. Using GoRB+GoRB Docker link on a SWARM cluster named "swarm-master". For this example, all of the services are running on the same node
swarm-node-1
. Trying to run a simple service on port 8000 but it fails. Using the docker images, kobolog/gorb in docker hub as of today. The only thing different from a standard deployment is that we are listening to the swarm event stream instead of the local HOST socket. If I use the HOST socket for the docker-link then it works correctly.GoRB service
GoRB Docker Link
And running a container
Executing:
Expect:
But Got:
Logs from GoRB Server
Logs from GoRB Linker
...
and after removing the motd container...
Query of the service from GoRB:
The Docker Hosts network config: