Scaling Azure Container Service with private ports on containers

In our organization, we are currently trying out the Azure Container Service with Docker Swarm. We have developed a Web API project based on .NET Core and created containers out of it. We have exposed the web api on Container’s Private Port (3000). We want to scale this to say 15 containers on three agent nodes while still accessing the web api through one single Azure load balancer url on public port 8080.

I believe we would need an Internal Load Balancer to do this but there is no documentation around it. I have seen this article on DC\OS but we are using Docker Swarm here. Any help?

  • Starting Docker Daemon Through Ansible
  • How to export/save an entire Docker container/image
  • Docker build “no such file or directory” but work with docker-compose
  • Creating multiple directories using docker RUN
  • In a Dockerfile, How to update PATH environment variable?
  • Docker and Java IDE integration
  • How to rename a docker image in the remote registry
  • Docker-compose throwing error
  • Install Oracle on docker centos container: Insufficient disk space
  • DockerFile does not appear in the docker deployment configuration list
  • Call From quickstart.cloudera/ to quickstart.cloudera:8020 failed on connection exception: Connection refused
  • Syntax highlighting for Dockerfile in Sublime Text?
  • One Solution collect form web for “Scaling Azure Container Service with private ports on containers”

    Azure Container Service use vanilla Docker Swarm so any load balancing solution for Swarm will work in ACS, e.g.

    Same is true for DC/OS, but in this case it is documented in “Load balance containers in an Azure Container Service cluster” –

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