Docker cloud builtin load balancing

When I deploy a new service with 3 containers via docker cloud I get 3 container endpoints and 1 service endpoint.

What I want to know is, how works the traffic forwarding on the service endpoint to the containers? Is there a built in load balancing or is this just a dns round robin?

  • Error checking context is accessible: 'can't stat '.gvfs''. Please check permissions and try again
  • Docker exec on an intermediate build image doesn't work
  • Can not deploy custom MFP docker image on IBM Bluemix
  • Docker Container: time/timezone wrong
  • Docker's NAT table output chain rule
  • Jenkins Plugin for Docker Engine on Windows
  • The service endpoint has a different IP than the containers, so where is this forwarding service running?

    Thank you guys for your help.

  • Cannot run nuttcp inside Docker
  • How to alter the official mongo docker for authentication and data separation?
  • Linux based docker images on Windows Server 2016 TP5
  • kafka on kubernetes cannot produce/consume topics (ClosedChannelException, ErrorLoggingCallback)
  • Telegraf unable to connect to InfluxDB
  • Slow codeception coverage in docker
  • One Solution collect form web for “Docker cloud builtin load balancing”

    I could find the answer here: https://docs.docker.com/docker-cloud/apps/ports/#/service-and-container-dns-endpoints

    It says about the service endpoint:

    This DNS endpoint (multiple A record) resolves to the IPs of the nodes where the containers are running, in a round-robin fashion.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.