Docker Cookbook

10.2 CI/CD: Building a Continuous Delivery Pipeline with Jenkins and Apache Mesos | 305

---

and the containers running on it (with exception of 
root
, which always has ID 0). To
solve this, you can use 
root
to start the Jenkins server.
For this, you need to add a new 
user
instruction to 
docker-compose.yml
:
jenkins:
image: Jenkins
user: root
volumes:
- jenkins-home:/var/jenkins_home
- /var/run/docker.sock:/var/run/docker.sock
- /usr/bin/docker:/usr/bin/docker
ports:
- 
"8080:8080"
Now, when you have a functional Jenkins server, you can deploy the Node.js applica‐
tion described in 
Recipe 10.1
.
In the Node.js recipe, you already have scripts to build, test, and push the image to a
Docker registry. You need to add a configuration file to schedule the application on
Mesos, using Marathon and another script to deploy the application.
You call the application configuration for Marathon 
app_marathon.json
:
{
"id"
:
"app"
,
"container"
:
{
"docker"
:
{
"image"
:
"localhost:5000/containersol/nodejs_app:latest"
,
"network"
:
"BRIDGE"
,
"portMappings"
:
[
{
"containerPort"
:
8000
,
"servicePort"
:
8000
}
]
}
},
"cpus"
:
0.2
,
"mem"
:
512.0
,
"instances"
:
1
}
This configuration uses our application Docker image that you are going to build
using Jenkins and deploy it on Mesos by using Marathon. This file also defines the
resources needed for your application and can also include a health check.
The last piece of the configuration is the deployment script that you are going to run
from Jenkins.
deploy.sh
:
#!/bin/bash
marathon=