Docker Compose to Orchestrate Containers

Docker Orchestration using Fig showed how to defining and control a multi-container service using Fig. Since then, Fig has been renamed to Docker Compose, or Compose for short.

First release of Compose was announced recently

Announcing @docker compose https://t.co/jJNvzbYCyk by @aanand @bfirsh & community!

— Docker (@docker) February 26, 2015

From github.com/docker/compose

Compose is a tool for defining and running complex applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.

Docker Compose uses the same API used by other Docker commands and tools.

This Tech Tip will rewrite Docker Orchestration using Fig blog to use Docker Compose. In other words, it will show how to run a Java EE 7 application that is deployed using MySQL and WildFly.

Lets get started!

Install Docker Compose

Install Compose as:

curl -L https://github.com/docker/compose/releases/download/1.1.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

curl -L https://github.com/docker/compose/releases/download/1.1.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose

chmod +x /usr/local/bin/docker-compose

Docker Compose Configuration File

Entry point to Compose is docker-compose.yml. To begin with, docker-compose tool also recognizes fig.yml file name but shows the following message:

fig.yml is deprecated and will not be supported in future. Please rename your config file to docker-compose.yml

fig.yml is deprecated and will not be supported in future. Please rename your config file to docker-compose.yml

And if both fig.yml and docker-compose.yml are available in the directory then the following message is shown:

Found multiple config files with supported names: docker-compose.yml, fig.yml
Using docker-compose.yml

Found multiple config files with supported names: docker-compose.yml, fig.yml

Using docker-compose.yml

Use the same configuration file from the previous blog and rename to docker-compose.yml:

mysqldb:
  image: mysql:latest
  environment:
    MYSQL_DATABASE: sample
    MYSQL_USER: mysql
    MYSQL_PASSWORD: mysql
    MYSQL_ROOT_PASSWORD: supersecret
mywildfly:
  image: arungupta/wildfly-mysql-javaee7
  links:
    - mysqldb:db
  ports:
    - 8080:8080

mysqldb:

image: mysql:latest

environment:

MYSQL_DATABASE: sample

MYSQL_USER: mysql

MYSQL_PASSWORD: mysql

MYSQL_ROOT_PASSWORD: supersecret

mywildfly:

image: arungupta/wildfly-mysql-javaee7

links:

- mysqldb:db

ports:

- 8080:8080

This YML-based configuration file has:

Two containers defined by the name “mysqldb” and “mywildfly”
Image names are defined using “image”
Environment variables for the MySQL container are defined in “environment”
MySQL container is linked with WildFly container using “links”
Port forwarding is achieved using “ports”

Start, Verify, Stop Docker Containers

All the containers can be started, in detached mode, by giving the command:

docker-compose up -d

docker-compose up -d

And that shows the output as:

Creating wildflymysqljavaee7_mysqldb_1...
Creating wildflymysqljavaee7_mywildfly_1...

Creating wildflymysqljavaee7_mysqldb_1...

Creating wildflymysqljavaee7_mywildfly_1...

Verify the containers as:

docker-compose ps
             Name                            Command               State                Ports               
-----------------------------------------------------------------------------------------------------------
wildflymysqljavaee7_mysqldb_1     /entrypoint.sh mysqld --da ...   Up      3306/tcp                         
wildflymysqljavaee7_mywildfly_1   /opt/jboss/wildfly/customi ...   Up      0.0.0.0:8080->8080/tcp, 9990/tcp

docker-compose ps

Name Command State Ports

-----------------------------------------------------------------------------------------------------------

wildflymysqljavaee7_mysqldb_1 /entrypoint.sh mysqld --da ... Up 3306/tcp

wildflymysqljavaee7_mywildfly_1 /opt/jboss/wildfly/customi ... Up 0.0.0.0:8080->8080/tcp, 9990/tcp

Logs for the containers can be seen as:

docker-compose logs

docker-compose logs

And shows the output as:

mywildfly_1 | => Starting WildFly server
mywildfly_1 | => Waiting for the server to boot
mywildfly_1 | =========================================================================
mywildfly_1 | 
mywildfly_1 |   JBoss Bootstrap Environment
mywildfly_1 | 
mywildfly_1 |   JBOSS_HOME: /opt/jboss/wildfly
mywildfly_1 | 
mywildfly_1 |   JAVA: /usr/lib/jvm/java/bin/java
mywildfly_1 | 
mywildfly_1 |   JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true


. . .


mywildfly_1 | 18:43:38,449 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (6, 'Raj')
mywildfly_1 | 18:43:38,452 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (7, 'Howard')
mywildfly_1 | 18:43:38,455 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (8, 'Priya')
mywildfly_1 | 18:43:39,714 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-9) Deploying javax.ws.rs.core.Application: class org.javaee7.samples.employees.MyApplication
mywildfly_1 | 18:43:39,751 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017534: Registered web context: /employees
mywildfly_1 | 18:43:39,805 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "employees.war" (runtime-name : "employees.war")
mywildfly_1 | 18:43:39,828 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
mywildfly_1 | 18:43:39,828 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
mywildfly_1 | 18:43:39,829 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 8393ms - Started 280 of 334 services (92 services are lazy, passive or on-demand)

mywildfly_1 | => Starting WildFly server

mywildfly_1 | => Waiting for the server to boot

mywildfly_1 | =========================================================================

mywildfly_1 |

mywildfly_1 | JBoss Bootstrap Environment

mywildfly_1 |

mywildfly_1 | JBOSS_HOME: /opt/jboss/wildfly

mywildfly_1 |

mywildfly_1 | JAVA: /usr/lib/jvm/java/bin/java

mywildfly_1 |

mywildfly_1 | JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

. . .

mywildfly_1 | 18:43:38,449 INFO [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (6, 'Raj')

mywildfly_1 | 18:43:38,452 INFO [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (7, 'Howard')

mywildfly_1 | 18:43:38,455 INFO [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (8, 'Priya')

mywildfly_1 | 18:43:39,714 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-9) Deploying javax.ws.rs.core.Application: class org.javaee7.samples.employees.MyApplication

mywildfly_1 | 18:43:39,751 INFO [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017534: Registered web context: /employees

mywildfly_1 | 18:43:39,805 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "employees.war" (runtime-name : "employees.war")

mywildfly_1 | 18:43:39,828 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

mywildfly_1 | 18:43:39,828 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

mywildfly_1 | 18:43:39,829 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 8393ms - Started 280 of 334 services (92 services are lazy, passive or on-demand)

Find the IP address of the host as:

boot2docker ip

boot2docker ip

And access the application as:

curl http://192.168.59.103:8080/employees/resources/employees/

curl http://192.168.59.103:8080/employees/resources/employees/

To see the output as:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><employee><id>1</id><name>Penny</name></employee><employee><id>2</id><name>Sheldon</name></employee><employee><id>3</id><name>Amy</name></employee><employee><id>4</id><name>Leonard</name></employee><employee><id>5</id><name>Bernadette</name></employee><employee><id>6</id><name>Raj</name></employee><employee><id>7</id><name>Howard</name></employee><employee><id>8</id><name>Priya</name></employee></collection>

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><employee><id>1</id><name>Penny</name></employee><employee><id>2</id><name>Sheldon</name></employee><employee><id>3</id><name>Amy</name></employee><employee><id>4</id><name>Leonard</name></employee><employee><id>5</id><name>Bernadette</name></employee><employee><id>6</id><name>Raj</name></employee><employee><id>7</id><name>Howard</name></employee><employee><id>8</id><name>Priya</name></employee></collection>

Or in the browser as:

Stop the containers as:

docker-compose stop

docker-compose stop

to see the output as:

Stopping wildflymysqljavaee7_mywildfly_1...
Stopping wildflymysqljavaee7_mysqldb_1...

Stopping wildflymysqljavaee7_mywildfly_1...

Stopping wildflymysqljavaee7_mysqldb_1...

Docker Compose Commands

Complete list of Docker Compose commands can be seen by typing docker-compose and shows the output as:

velopment environments using Docker.

Usage:
  docker-compose [options] [COMMAND] [ARGS...]
  docker-compose -h|--help

Options:
  --verbose                 Show more output
  --version                 Print version and exit
  -f, --file FILE           Specify an alternate compose file (default: docker-compose.yml)
  -p, --project-name NAME   Specify an alternate project name (default: directory name)

Commands:
  build     Build or rebuild services
  help      Get help on a command
  kill      Kill containers
  logs      View output from containers
  port      Print the public port for a port binding
  ps        List containers
  pull      Pulls service images
  rm        Remove stopped containers
  run       Run a one-off command
  scale     Set number of containers for a service
  start     Start services
  stop      Stop services
  restart   Restart services
  up        Create and start containers

velopment environments using Docker.

Usage:

docker-compose [options] [COMMAND] [ARGS...]

docker-compose -h|--help

Options:

--verbose Show more output

--version Print version and exit

-f, --file FILE Specify an alternate compose file (default: docker-compose.yml)

-p, --project-name NAME Specify an alternate project name (default: directory name)

Commands:

build Build or rebuild services

help Get help on a command

kill Kill containers

logs View output from containers

port Print the public port for a port binding

ps List containers

pull Pulls service images

rm Remove stopped containers

run Run a one-off command

scale Set number of containers for a service

start Start services

stop Stop services

restart Restart services

up Create and start containers

A subsequent blog will likely play with scale command.

Help for each command is shown by typing -h after the command name. For example, help for run command is shown as:

docker-compose run -h
Run a one-off command on a service.

For example:

    $ docker-compose run web python manage.py shell

By default, linked services will be started, unless they are already
running. If you do not want to start linked services, use
`docker-compose run --no-deps SERVICE COMMAND [ARGS...]`.

Usage: run [options] [-e KEY=VAL...] SERVICE [COMMAND] [ARGS...]

Options:
    --allow-insecure-ssl  Allow insecure connections to the docker
                          registry
    -d                    Detached mode: Run container in the background, print
                          new container name.
    --entrypoint CMD      Override the entrypoint of the image.
    -e KEY=VAL            Set an environment variable (can be used multiple times)
    --no-deps             Don't start linked services.
    --rm                  Remove container after run. Ignored in detached mode.
    --service-ports       Run command with the service's ports enabled and mapped
                          to the host.
    -T                    Disable pseudo-tty allocation. By default `docker-compose run`
                          allocates a TTY.

docker-compose run -h

Run a one-off command on a service.

For example:

$ docker-compose run web python manage.py shell

By default, linked services will be started, unless they are already

running. If you do not want to start linked services, use

`docker-compose run --no-deps SERVICE COMMAND [ARGS...]`.

Usage: run [options] [-e KEY=VAL...] SERVICE [COMMAND] [ARGS...]

Options:

--allow-insecure-ssl Allow insecure connections to the docker

registry

-d Detached mode: Run container in the background, print

new container name.

--entrypoint CMD Override the entrypoint of the image.

-e KEY=VAL Set an environment variable (can be used multiple times)

--no-deps Don't start linked services.

--rm Remove container after run. Ignored in detached mode.

--service-ports Run command with the service's ports enabled and mapped

to the host.

-T Disable pseudo-tty allocation. By default `docker-compose run`

allocates a TTY.

Enjoy!

Be Sociable, Share!

15 thoughts on “Docker Compose to Orchestrate Containers – Tech Tip #77”

AJN says:

March 7, 2015 at 2:59 am

Nice tip!
Is it possible to use pipework with Docker-compose?
arungupta says:

March 7, 2015 at 11:14 am

Seems like a pending issue at: https://github.com/docker/compose/issues/1003
Pingback: So, you’d like to start using Docker for Java EE applications? 9 Recipes for greatness | Ceiba3D Studio
Pingback: 9 Docker recipes for Java EE Applications | Ceiba3D Studio
Pingback: Docker Compose on Windows with Python And Banon | Social Marketing by WordPress
Pingback: Docker 1.7.0, Docker Machine 0.3.0, Docker Compose 1.3.0, Docker Swarm 0.3.0 - Miles to go 2.0 ...
Pingback: Docker 1.7.0, Docker Machine 0.3.0, Docker Compose 1.3.0, Docker Swarm 0.3.0 | Social Marketing by WordPress
Pingback: Multi-container Applications using Docker Compose and Swarm - Miles to go 2.0 ...
Pingback: Multi-container Applications using Docker Compose and Swarm | Social Marketing by WordPress
Hariharan says:

August 1, 2015 at 10:00 am

Question.. How do i use cid=$(ifconfig eth0 | grep ‘inet addr:’ | cut -d: -f2…) inside a docker-compose.yml file?
arungupta says:

August 1, 2015 at 11:22 am

Hariharan,

Not sure if this is possible, file a bug?
eric hebert says:

August 31, 2015 at 8:14 am

i get troubleshooting in running [root@ix1-dv-c6-survey-01 javaee7-arungupta]# docker run arungupta/wildfly-mysql-javaee7
/bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: Permission denied.
I am on centOS 6.7, SELinux disabled (https://github.com/docker/docker/issues/7318)
uname -a
Linux 020e23a319a9 2.6.32-573.3.1.el6.x86_64 #1 SMP Thu Aug 13 22:55:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
mount | grep ‘ / ‘
/dev/mapper/VG0-lv_root on / type ext4 (rw)
[root@ix1-dv-c6-survey-01 javaee7-arungupta]# docker version
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d
OS/Arch (server): linux/amd64
arungupta says:

August 31, 2015 at 5:11 pm

Are you creating your own images? Or using the ones that already exist?
Pingback: Beyond Docker Compose
Pingback: Beyond Docker Compose | 神刀安全网

Miles to go 4.0 …

Arun Gupta is a technology enthusiast, avid runner, author of a best-selling book, globe trotter, a community guy, Java Champion, JavaOne Rockstar, JUG Leader, Minecraft Modder, NetBeans Dream Teamer, Devoxx4Kids-er, Docker Captain and works at AWS.

Docker Compose to Orchestrate Containers – Tech Tip #77

Install Docker Compose

Docker Compose Configuration File

Start, Verify, Stop Docker Containers

Docker Compose Commands

15 thoughts on “Docker Compose to Orchestrate Containers – Tech Tip #77”

Leave a Reply Cancel reply