Docker Minecraft Host

I am trying to host Minecraft servers in docker containers on an ec2 instance, and point a different subdomain to each container, for example

a.example.com -> container 1

  • RDS ENV variables in elastic beanstalk
  • How to deploy a Docker container on EC2 ECS from Docker Hub private repo?
  • Motivation for putting Docker containers inside an AWS EC2 instance
  • apt-get in docker behind corporate proxy
  • web server running inside a docker container running inside an EC2 instance responses very slowly
  • slow or timeout of dns resolving inside docker
  • b.example.com -> container 2

    c.example.com -> container 3

    …and so on.

    If these containers were running a website, I could forward the traffic with Apache, or node-http-proxy, etc. But because these servers are running TCP services, I cannot route the traffic this way.

    Is this possible? And if so, how?

  • docker pull with digest works but unable to find repo in the catalog?
  • Running a Docker container on AWS Elastic Beanstalk - Where is my web app?
  • How can I read data from another data bucket with Google Datalab ipython notebook?
  • How to exit “docker run” containers once the script those containers execute calls exit()
  • what is the alpine linux equivalent package of ubuntu's libarmadillo-dev? [closed]
  • Unable to push windows docker image to Artifactory
  • 2 Solutions collect form web for “Docker Minecraft Host”

    The Minecraft client has supported SRV DNS records for a while now (since 1.3.1 according to google). I suggest you assign your Docker containers a stable set of port mapping with the -p flag, and then create SRV records for each FQDN pointing to the same IP but different ports.

    Google gives several hits on the SRV entry format – this one is from the main MCF site: http://www.minecraftforum.net/topic/1922138-using-srv-records-to-hide-ports-on-your-server-ip/

    I have four MC servers running on the same physical host with a single IP address, each with a separate friendly entry for players to use in the Minecraft client, so none of my users need to remember a port. It did cause confusion for a couple of my more technical players when they had a connectivity issue, tested with dig/ping, then thought the DNS resolution was broken when there was no A record to be found. Overall, I think that’s a very small downside.

    Doesn’t HAProxy http://haproxy.1wt.eu/ route tcp traffic?

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