Skip to content

Latest commit

 

History

History
39 lines (31 loc) · 2.89 KB

README.md

File metadata and controls

39 lines (31 loc) · 2.89 KB

Container Orchestration using Docker tools: Engine, Swarm, Machine, Compose

This demo uses the latest networking features introduced in Docker 1.9 and shows how machine, compose and swarm work together to help you orchestrate containers. The core of the demo comes from @dave-tucker, you can find his scripts at https://github.com/dave-tucker/docker-network-demos. The application used in this demo is spring-doge by @joshlong and @philwebb, a Spring Boot Java application using MongoDB and MongoFS.

I have shown it at JavaOne 2015, video of the demo, slides

You need Docker 1.10, and corresponding latest versions of compose and machine, which you can install with docker-toolbox 1.10.0 As of today you need:

  • docker 1.10 and above
  • docker-machine 0.6.0 and above
  • docker-compose 1.6.0

If you are still using 1.9, look at previous versions of this repo.

To run it:

./swarm-local.sh
eval $(docker-machine env --swarm swl-demo0)
docker-compose up -d
docker-compose scale web=3

Then in another terminal:

open http://$(docker-machine ip swl-demo0):8080

old-docker-compose.yml is the old style compose for the spring-doge app, using links. docker-compose.yml is the new style compose file without links, leveraging the new docker networking support in compose. It uses:

  • environment variable container_name to force the name of the mongo container to be db (else compose will call it orchestrationnetworking_mongo_1). This will be the hostname that networking will use for that container.
  • "label:storage=ssd" environment variable to ask Swarm to schedule the mongo container on a host labeled with ssd storage (in our example swl-demo1)
  • environment variable "affinity:com.docker.compose.service!=db" to ask Swarm to schedule the web container on a host different than the one where the db is hosted.
  • environment variable MONGODB_URI=mongodb://db:27017/test that is expected from the spring-doge application that serves our web tier to connect to the database container. Here we leverage the fact that networking will assign db as the hostname.
  • networks section

This example shows:

  • using docker-machine to provision a docker engine. Use docker to launch consul.
  • using docker-machine to provision a swarm cluster, using the previous consul instance for swarm discovery and networking config store.
  • using docker machine --engine-label option to apply labels to some of our swarm cluster engines, that we can use for scheduling constraints.
  • using docker-compose swarm and networking integrations to schedule a Spring Boot app using Mongodb on a Swarm cluster.