This document provides an overview of using Docker containers to develop and deploy applications. It discusses: 1. Using base Docker images to define common environments and then building application images on top of these bases. 2. Describing infrastructure and applications as code using Dockerfiles so new developers can quickly get started coding and deployments are automated and consistent. 3. How configurations can be managed separately from code to deploy the same application code to different environments like development, test, and production with only configuration changes.

1. Aug, 2018
Takahiro Yamaki
EC Marketplace RMS Development Department
Rakuten, Inc.

2. 2
2. System relation map

3. 3
Reference: https://blog.netapp.com/blogs/containers-vs-vms/
More info!
Docker merit
Small size
Effective resource sharing
High speed spin up
… etc.

4. 4
Application
Docker Image
Base
Docker Image
•
• …
•
• …
•
• …
Environment variables are
attached at booting
1st step
2nd step

5. 5
FROM php/apache:latest
: "Application directories“ && ¥
mkdir -p /project/public && ¥
: "Application User“ && ¥
groupadd -g 10000 hoge && ¥
useradd -u 10001 -g hoge -s /bin/bash hogeuser && ¥
: "Owner change" && ¥
chown -R hogeuser:hoge /project/public
COPY ./init.sh /opt/docker/provision/entrypoint.d/
ENV WEB_DOCUMENT_ROOT /project/public
$ sudo docker build –t hoge-application-base:1.0 .
Infrastructure as code !!!
Public images

6. 6Reference: https://hub.docker.com/
You don’t need to make
these servers from
scratch anymore!

7. 7
FROM hoge-application-base:1.0
COPY ./sample-app/public /project/public/
$ sudo docker build -t hoge-application:1.0 .
Application release steps as code

8. 8
{"env": {
“A-API-URL":"http://stg-aaa-api.jp.local/1.1.0"
,”AAA-API-KEY”:”abcdefg”
…
env.json
runtimi.conf
CPU=0.1
MEM=1024
INSTANCES=1
….

9. 9
Application
Image
Base
Image
Base
Image
Snapshot Ver.
Application
Image
Base
Image
Release ver.
DEV env. STG(QA) env. PRO env.
+DEV conf +STG conf +PROD conf
Local env.
+ Local conf
codes
Container management platformDocker-compose
Quality assured
docker image will be
deployed to PROD
env after QA test.
Differences are
only config files

10. 10
Is it necessary to maintain your server construction manual?

11. 11
Is it necessary to maintain your server construction manual?
 No!!! Infrastructure as code!!!
FROM tomcat:8.0-jre8
: "Application directories“ && ¥
mkdir -p /project/public && ¥
: "Application User“ && ¥
….
Base Dockerfile ver 1 Base Dockerfile ver 2
FROM tomcat:8.0-jre8
: "Application directories“ && ¥
mkdir -p /project/public && ¥
mkdir -p /var/log/aaa && ¥
: "Application User“ && ¥
….

12. 12
How long is it likely take for a new joiner to start his/her coding?

13. 13
How long is it likely take for a new joiner to start his/her coding?
Very Soon!!!
$ git clone …..
$ cd /path/to/target/dir/
$ docker-compose up -d

14. 14
How can we version up the middleware? (ex. tomcat, jdk, php, etc.)

15. 15
How can we version up the middleware? (ex. tomcat, jdk, php, etc.)
 Just change public image setting
Base Dockerfile ver 2 Base Dockerfile ver 3
FROM tomcat:8.0-jre8
: "Application directories“ && ¥
mkdir -p /project/public && ¥
mkdir -p /var/log/aaa && ¥
: "Application User“ && ¥
….
FROM tomcat:9.0-jre8
: "Application directories“ && ¥
mkdir -p /project/public && ¥
mkdir -p /var/log/aaa && ¥
: "Application User“ && ¥
….

16. 16
How can we increase the machine spec? (scale up)

17. 17
How can we increase the machine spec? (scale up)
 Edit Variables and Restart
runtime.conf
CPU=0.1
MEM=1024
INSTANCES=1
….
CPU=0.2
MEM=2048
INSTANCES=1
….

18. 18
How can we increase # of machines? (scale out)

19. 19
How can we increase # of machines? (scale out)
 Edit Variables and Restart
runtimi.conf
CPU=0.1
MEM=1024
INSTANCES=1
….
CPU=0.1
MEM=1024
INSTANCES=2
….

20. 20
2. System relation map

21. 21
Application
Image
Base
Image
Base
Image
Snapshot Ver.
Application
Image
Base
Image
Release ver.
DEV env. STG(QA) env. PRO env.
+DEV conf +STG conf +PROD conf
Local env.
+ Local conf
codes
Container management platformDocker-compose

22. 22
git clone
build Base image
push image
git clone
pull Base image
build app image
push image
Trigger
deployment
git clone
pull App image
docker run
Base
Image
confcodes
Base
Dockerfile
Application
Dockerfile
System start!
App
Image
Container management
platform
git
maven
Artifacts Library
Private Docker Registry

23. 23
2. System relation map

24. 24
git clone
build image
extract artifacts
codesDockerfile
git
npm build script
Using -v option (docker mount function)
Generated artifacts are included
in an Application image

25. 25
FROM node:10.5-alpine
LABEL maintainer “hoge <hoge@example.com>"
COPY ./sample-front-dev/package.json /tmp/install/
….
….
COPY ./sample-front-dev/src /tmp/install/src
COPY ./npm-build.sh /tmp/install/
WORKDIR /tmp/install/
RUN set -x && ¥
npm config set https-proxy http://hoge.proxy:9999 && ¥
npm install
CMD ["sh", "/tmp/install/npm-build.sh"]
Dockerfile
#!/bin/sh
npm run build
cp /tmp/install/dist/css/*.css /tmp/artifacts/
cp /tmp/install/dist/js/*.js /tmp/artifacts/
chmod 777 /tmp/artifacts/*
ls -l /tmp/artifacts/
npm-build.sh

26. 26
Swagger Editor (local docker)
Edit & check Preview
openapi.yaml
swaggerapi/swagger-ui
https://hub.docker.com/r/swaggerapi/swagger-ui/
git
Swagger UI
Container management
platform
private
Docker Registry

27. 27
From swaggerapi/swagger-ui
LABEL maintainer “hoge <hoge@sample.com>"
COPY ./spec/openapi.yaml /usr/share/nginx/html/
Dockerfile
{"env": {"SWAGGER_JSON":"openapi.yaml", "API_URL":"http://hoge.sample.intra.com/openapi.yaml"},
"portMappings": [{"containerPort": 0}]}
config

28. 28
git
Container management
platform
private
Docker Registry
Base image
Mock api
soapui-mock-project.xml
SoapUI-x.x.x-linux-bin.tar.gz
entrypoint.sh

29. 29
From java:openjdk-8u111-jre-alpine
LABEL maintainer “hoge <hoge@sample.com>"
COPY SoapUI-5.4.0-linux-bin.tar.gz /opt/
COPY entrypoint.sh /
RUN chmod 755 /entrypoint.sh && ¥
cd /opt/ && ¥
tar -zxf SoapUI-5.4.0-linux-bin.tar.gz && ¥
mv /opt/SoapUI-5.4.0 /opt/soapui && ¥
rm -f SoapUI-5.4.0-linux-bin.tar.gz && ¥
echo "0 1 * * * rm -f /root/*.log" >> /etc/crontabs/root
CMD ["sh", "/entrypoint.sh"]
<base>Dockerfile <application> Dockerfile
From mock-docker-base-sample:1.0
LABEL maintainer “hoge <hoge@sample.com>“
ENV MOCKSERVICE_NAME="mock“ ¥
MOCKSERVICE_PORT="8080“ ¥
PROJECT_FILE="/root/soapui-mock-project.xml"
COPY soapui-mock-project.xml /root/

30. 30