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?

  • java.util.regex.PatternSyntaxException when using sbt docker:publishLocal
  • Chokidar isn't picking up file changes inside docker container
  • Docker: “lstat no such file or directory” error when building image. File is there
  • Docker. npm install -> Error: getaddrinfo ENOTFOUND
  • what is a best way to store data in docker?
  • docker stack deploy from private repo
  • The service endpoint has a different IP than the containers, so where is this forwarding service running?

    Thank you guys for your help.

  • Docker for Mac - run X11 applications without an active internet connection
  • How to Copy file to stopped docker container
  • Unable to Register Chaincode & Successfully Start Blockchain Network
  • Container spawning for interactive tutorial
  • Docker pull fails to lookup index.docker.io on 127.0.1.1:53 (cannot unmarshal DNS message)
  • Change Java “SecureRandom” in Dockerfile
  • 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.