Dockerize your life

What is docker?
Check installation
Do it yourself
- Extra: Docker pipelines
Para los putos amos !!!

What is Docker?

Open source project
allows a easy way to package, run and share your app in a isolated environment (container)

Difference between VM and Container

Benefits

Flexible: Even the most complex applications can be containerized.
Lightweight: Containers leverage and share the host kernel, making them much more efficient in terms of system resources than virtual machines.
Portable: You can build locally, deploy to the cloud, and run anywhere.
Loosely coupled: Containers are highly self sufficient and encapsulated, allowing you to replace or upgrade one without disrupting others.
Scalable: You can increase and automatically distribute container replicas across a datacenter.
Secure: Containers apply aggressive constraints and isolations to processes without any configuration required on the part of the user.

Docker architecture

Docker life cycle

<Mermaid chart={stateDiagram Devs --> Registry: push app Devs --> Server: run app Registry --> Server: pull app state Devs { docker_build --> docker_push } state Registry { docker_images } state Server { docker_pull --> docker_run }}/>

Empathy life cycle

<Mermaid chart={stateDiagram Dev --> Git Git --> Jenkins Jenkins --> Registry: push app Jenkins --> ServerProd: run app Registry --> ServerProd: pull app state Dev { git_commit --> git_push } state Jenkins { git_pull --> docker_build docker_build --> docker_push } state Registry { docker_image } state ServerProd { docker_pull --> docker_run }}/>

First steps

Check you have installed Docker:

docker --version

You should see something like:

Docker version 19.03.8, build afacb8b

Check that you can run a container:

docker run hello-world

You should see something like:

Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
1b930d010525: Pull complete
Digest: sha256:f9dfddf63636d84ef479d645ab5885156ae030f611a56f3a7ac7f2fdd86d7e4e
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

Docker build

Clone this repository running:

git clone https://github.com/empathyco/dockerizeyourlife.git

Go to the folder:

cd dockerizeyourlife

Check the Dockerfile in the root folder:

# You can extend an existing image
FROM ubuntu
# Add metadata
LABEL "com.empathy.talk"="Dockerize you live"
LABEL maintainer="cesarg@empathy.co"
# Expose ports
EXPOSE 3000
# Set the user
USER root
# Set build arguments
ARG EMAIL
ARG COMPANY=empathy
# It is possible to run cmd
RUN apt update && apt install -y vim
RUN mkdir /app /myvol
# You can set enviromentals vars
ENV COMPANY "empathy"
# You can copy files
ADD app /app
COPY README.md /app/
RUN sed -i 's/EMAIL/'${EMAIL}'/' /app/vim.md
# Add a volume
VOLUME /myvol
# You can set the working directory
WORKDIR /app
# Set a healthcheck
HEALTHCHECK --interval=5m --timeout=3s \
  CMD cat /app/vim.md || exit 1
# Set a init cmd
#CMD ["vim", "/app/vim.md"]
ENTRYPOINT ["vim", "/app/vim.md"]

Run the build:

docker build --build-arg EMAIL="yourname" -t test-empathy -f Dockerfile .

You should see something like:

# Build start  
Sending build context to Docker daemon  416.3kB
# We download the parent image
Step 1/16 : FROM ubuntu
 ---> 72300a873c2c
# For each line of the Dockerfile docker creates a new layer
Step 2/16 : LABEL "com.empathy.talk"="Dockerize your life"
 ---> Using cache
 ---> 7b89f8b0e00f
 # This layer a cached, next time we build the image the layer will be not rebuild
 # this reduce the build time
Step 3/16 : LABEL maintainer="cesarg@empathy.co"
 ---> Using cache
 ---> 07523f71102e
 # If you modify the step/line in the Dockerfile all next steps will be rebuild.
 # This also happen if you copy a file as you create a new layer
Step 4/16 : EXPOSE 3000
 ---> Using cache
 ---> 3ad6fad071cf
Step 5/16 : USER root
 ---> Using cache
 ---> b80a693c5e18
Step 6/16 : ARG EMAIL
 ---> Using cache
 ---> 2632e3fe7fa9
Step 7/16 : ARG COMPANY=empathy
 ---> Using cache
 ---> e9b4c8100f7f
Step 8/16 : RUN apt update && apt install -y vim
 ---> Using cache
 ---> a4703eb24b67
Step 9/16 : RUN mkdir /app /myvol
 ---> Using cache
 ---> 4733de4d2bea
Step 10/16 : ENV MY_VAR "empathy"
 ---> Using cache
 ---> 42d517fb07df
Step 11/16 : ADD app /app
 ---> Using cache
 ---> 7bafd5fe61b6
Step 12/16 : COPY README.md /app/
 ---> 28df5342e515
Step 13/16 : RUN sed -i 's/EMAIL/'${EMAIL}'/' /app/vim.md
 ---> Running in 59844c6bb6d9
Removing intermediate container 59844c6bb6d9
 ---> ff4b84ffa6eb
Step 14/16 : WORKDIR /app
 ---> Running in 45a37a114dc4
Removing intermediate container 45a37a114dc4
 ---> 8babcd3c14c9
Step 15/16 : HEALTHCHECK --interval=5m --timeout=3s   CMD cat /app/vim.md || exit 1
 ---> Running in e8ca831f36f3
Removing intermediate container e8ca831f36f3
 ---> e177696340fb
Step 16/16 : ENTRYPOINT ["vim", "/app/vim.md"]
 ---> Running in 2394eaf74011
Removing intermediate container 2394eaf74011
 ---> b0e7ea6c9093
Successfully built b0e7ea6c9093
Successfully tagged test-empathy:latest
....

Docker images

Lets see the image created:

docker images | grep test-empathy

You should see something like:

REPOSITORY        TAG                    IMAGE ID            CREATED             SIZE
test-empathy      latest                 ac37b42d6e11        25 minutes ago      153MB

We can delete also the image. Check what rmi command does:

docker rmi --help

You should see something like:

Usage:	docker rmi [OPTIONS] IMAGE [IMAGE...]

Remove one or more images

Options:
  -f, --force      Force removal of the image
      --no-prune   Do not delete untagged parents

Lets delete our image:

docker rmi test-empathy -f

You should see something like:

Untagged: test-empathy:latest
# It delete each of the layer that we have created in the Dockerfile
Deleted: sha256:b0e7ea6c909307294c26d736e943a143e422b945c7a712366d99e03c54d14c83
# It is important to group proper the instructions/layer to avoid rebuilding
# layers that we can cache
Deleted: sha256:e177696340fb75a73f048f5bc113fcb21b268b1ca26d67eb5efed19287421582
Deleted: sha256:8babcd3c14c9a927540d04ec02b5a473a8fac60a4ee35392ce95a528eb0be52a
Deleted: sha256:ff4b84ffa6ebd221c557bdba9b1ff90afc6999264f64fa57f27b2a63ee998432
Deleted: sha256:60a8eced2e81794b24f050a729d93a969803a4fb3f6bc15b130603c613cc8194
Deleted: sha256:28df5342e515b7c8187b58fee4cc0d44609ddbd3cef3a27aad455c633d2fa8f1
Deleted: sha256:0c5f88939e979d87ac57689e48de4f4be21daa1c60e1888707a6dfce5c45164d

Docker run

Create again the image:

docker build --build-arg EMAIL="yourname" -t test-empathy -f Dockerfile .

Run the image by creating a container:

docker run -e COMPANY=empathy -t test-empathy

Open a new terminal and run:

docker ps

You should see something like:

CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                             PORTS               NAMES
cffa30d1473c        test-empathy        "vim /app/vim.md"   16 seconds ago      Up 16 seconds (health: starting)   3000/tcp            loving_mclean

Stop the container changing the CONTAINER_ID tag with the one shown before:

docker stop <CONTAINER_ID>

We can delete the container changing the CONTAINER_ID tag with the one shown before:

docker rm <CONTAINER_ID>

Expose port

Go to golang-app path:

cd golang-app

Check the Dockerfile:

FROM golang:1.7.3
WORKDIR /go/src/github.com/empathy/dockerize/
COPY main.go .
RUN go get -d -v golang.org/x/net/html \
  && CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app .
CMD ["/go/src/github.com/empathy/dockerize/app"]

Build the image:

docker build -t empathy-example-golang .

Set the ports we want to use:

export PORT_INTERNAL=5000 # Use our app
export PORT_EXTERNAL=5001 # Use our host (your machine)

Run the container forwarding the port:

-it: Run tty mode.
--name: Container name.
-e: Set env var for the port in our app.
-p: Set port to forward in host.

docker run -it --name golang-app -e PORT="${PORT_INTERNAL}" -p "${PORT_EXTERNAL}:${PORT_INTERNAL}" empathy-example-golang

Test the running app in a new terminal window:

curl localhost:9000/hola_que_ase

You should see something like:

curl: (7) Failed to connect to localhost port 9000: Connection refused

Try again:

curl localhost:5001/hola_que_ase

Now You should see something like:

Hello from Empathy Golang service hola_que_ase!

Docker ps

We can check running container by doing:

docker ps

You should see something like:

CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                    NAMES
03879f54c875        empathy-example-golang   "/go/src/github.com/…"   4 minutes ago       Up 4 minutes        0.0.0.0:5001->5000/tcp   golang-app

We can stop/start the container:

docker stop golang-app

Check again:

docker ps

Nothing should appear under the header.

But... Check all of them:

docker ps -a | grep golang-app

You should see something like:

CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                    NAMES
aaa9c1e1f618        empathy-example-golang   "/go/src/github.com/…"   50 seconds ago       Exited (0) 2 seconds ago                     golang-app

Start it again:

docker start golang-app

Check containers again:

docker ps

You should see something like:

CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                    NAMES
aaa9c1e1f618        empathy-example-golang   "/go/src/github.com/…"   2 seconds ago       Up 1 second         0.0.0.0:5000->9000/tcp   golang-app

Stop again to free the port:

docker stop golang-app

Docker inspect

Show more info about the container:

docker inspect golang-app

Docker tag

Change the name of the image:

export OLD_IMAGE_NAME="empathy-example-golang"
export NEW_IMAGE_NAME="empathyco/golang"
export BASE64_EMAIL=`echo "youremail@empathy.co" | base64`
export DOCKER_TAG=`echo "${BASE64_EMAIL//=}"`
docker tag "${OLD_IMAGE_NAME}" "${NEW_IMAGE_NAME}:${DOCKER_TAG}"

Inspect the images:

docker images

You should see something like:

REPOSITORY               TAG                            IMAGE ID            CREATED             SIZE
empathy-example-golang   latest                         ef40c2534f4a        38 minutes ago      697MB
empathyco/golang         eW91cmVtYWlsQGVtcGF0aHkuY28K   ef40c2534f4a        38 minutes ago      697MB

Docker login

Login in a remote registry to share our images and download others. You can login in multiple registry.

Check the command:

docker login --help

You should see something like:

Usage:	docker login [OPTIONS] [SERVER]

Log in to a Docker registry.
If no server is specified, the default is defined by the daemon.

Options:
  -p, --password string   Password
      --password-stdin    Take the password from stdin
  -u, --username string   Username

Login into hub.docker.com:

docker login

You should see something like:

Authenticating with existing credentials...
Login Succeeded

Docker push

We can push our images to share it.

Set variables:

# This is the name of the repository
# Format: ${REPOSITORY_URL}/${IMAGE_NAME}:${TAG}
# the default tag is latest
# the default registry is docker.io
# example: eu.gcr.io/empathy/golang:master
export IMAGE_NAME="empathyco/golang"
export BASE64_EMAIL=`echo "youremail@empathy.co" | base64`
export TAG=`echo "${BASE64_EMAIL//=}"`

Push the image:

docker push "${IMAGE_NAME}:${TAG}"

:::info Time to take a ☕️ meanwhile docker push ends. :::

Docker pull

Now, we can share our image, ask for the email of one of your colleagues and hash it:

export BASE64_EMAIL=`echo "youcolleagueemail@empathy.co" | base64`
export COLLEAGUE_EMAIL_HASH=`echo "${BASE64_EMAIL//=}"`
export IMAGE_NAME=empathy/golang

Download the new image

docker pull "${IMAGE_NAME}:${COLLEAGUE_EMAIL_HASH}"

Run it:

docker run "${IMAGE_NAME}:${COLLEAGUE_EMAIL_HASH}"

Other images

As you could see in hub.docker.com there are tones of other apps. Lets run a mongo (https://hub.docker.com/_/mongo):

docker pull mongo

You should see something like:

Using default tag: latest
latest: Pulling from library/mongo
5bed26d33875: Already exists
f11b29a9c730: Already exists
930bda195c84: Already exists
78bf9a5ad49e: Already exists
3d7fb3809884: Already exists
a7237292ff8a: Already exists
c936e28b5159: Already exists
3fb56b127f30: Already exists
c54a0478af29: Already exists
ffc3a4dd1cdc: Already exists
236ffdb10499: Already exists
c33efe03b109: Already exists
1d3609ce2ac9: Already exists
Digest: sha256:1e33093260855e83baee0237e29947e243818c58a1d37b1022909e227f624d7a
Status: Downloaded newer image for mongo:latest
docker.io/library/mongo:latest

You can also download a specific version by changing the tag:

docker pull mongo:3.6.17

Lets run it:

-d: Detach mode to run in the background.
--name: Container name.
--rm: Remove the container after termination.

docker run --rm --name mongodb -d -p 9000:27017 mongo

Check mongo is running:

docker ps

You should see something like:

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                      NAMES
f55ff4c5015a        mongo               "docker-entrypoint.s…"   22 minutes ago      Up 1 second         0.0.0.0:27017->27017/tcp   mongodb

Now we can connect to localhost:

mongo mongodb://localhost:9000

:::caution You will need a mongodb CLI to connect. :::

You should see something like:

MongoDB shell version v4.2.0
connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("225866a8-767a-4648-8798-95043701e5e6") }
MongoDB server version: 4.2.5
Server has startup warnings:
2020-04-15T11:01:35.611+0000 I  STORAGE  [initandlisten]
2020-04-15T11:01:35.611+0000 I  STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2020-04-15T11:01:35.611+0000 I  STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2020-04-15T11:01:36.392+0000 I  CONTROL  [initandlisten]
2020-04-15T11:01:36.392+0000 I  CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2020-04-15T11:01:36.392+0000 I  CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2020-04-15T11:01:36.392+0000 I  CONTROL  [initandlisten]
---
Enable MongoDBs free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).

The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.

To enable free monitoring, run the following command: db.enableFreeMonitoring()
To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
---

Run inside mongodb terminal to show databases:

show dbs

You should see something like:

admin   0.000GB
config  0.000GB
local   0.000GB

Exit from mongo:

exit

Stop container for now:

docker stop mongodb

Docker volume

When we delete a container all data that is stored is deleted also. For that we have docker volume:

docker volume create mongodbdata

List the volume:

docker volume ls

You should see somthing like:

DRIVER              VOLUME NAME
local               mongodbdata

Inspect the volume:

docker volume inspect mongodbdata

You should see something like:

[
    {
        "CreatedAt": "2020-04-15T11:15:14Z",
        "Driver": "local",
        "Labels": {},
        "Mountpoint": "/var/lib/docker/volumes/mongodbdata/_data",
        "Name": "mongodbdata",
        "Options": {},
        "Scope": "local"
    }
]

Delete it:

docker volume rm mongodbdata

And create it again!

docker volume create mongodbdata

Run the container:

docker run --name mongodb -v mongodbdata:/data/db -p 9000:27017 mongo

Connect to mongo in other terminal window:

mongo mongodb://localhost:9000

Lets insert some data:

db.tutorial.insert({"name":"dockerize"});
db.tutorial.findOne();

You should see something like:

{ "_id" : ObjectId("5e96efcbd9af284a9809ac0a"), "name" : "dockerize" }

Exit from mongo:

exit

Delete the container:

docker stop mongodb && docker rm mongodb

Now lets run it again:

docker run --name mongodb -v mongodbdata:/data/db -p 9000:27017 -d mongo

Connect to mongo:

mongo mongodb://localhost:9000

Check that the data is still there:

db.tutorial.findOne();

You should see something like:

{ "_id" : ObjectId("5e96efcbd9af284a9809ac0a"), "name" : "dockerize" }

:::tip You can also create anonymous volume by doing:

mkdir data
export PATH_TO_YOUR_FOLDER="${PWD}/data"
docker run --name mongodb -v ${PATH_TO_YOUR_FOLDER}:/data/db -p 9000:27017 mongo

:::

Docker exec

You can run cmd also in the container:

-it: tty activated, so keyboard can be use.
mongodb: Container name.
/bin/bash: CMD you want to run.

docker exec -it mongodb /bin/bash root@f55ff4c5015a:/

Do it yourself

Now that we know the basic of docker (networking is missing but it will be cover in future talk), let see what you got.

Navigate to node-app, there you will see an small aplication in nodejs. This app is a webserver that is exposed in the port set in the env var APP_PORT.

:::info For this exercise you will need node.js and jq.

Install node.js

brew install node

Install jq

brew install jq

:::

Navigate to path:

cd ../node-app

Install dependencies:

npm install

Run the app:

export APP_PORT=5000
export EMAIL="adasfef" 
node app.js

You should see something like:

Example app listening at http://localhost:5000

The webapp has an endpoint configured to run the following script:

#!/bin/bash
set -xeu
VERSION=$(cat package.json | jq '.version')
MESSAGE_PATH=Message.txt
sed -i 's/VERSION/'${VERSION}'/' /opt/Message.txt
sed -i 's/EMAIL/'${1}'/g' /opt/Message.txt
cat /opt/Message.txt

Call the app just running:

export APP_PORT=5000
curl "localhost:${APP_PORT}"

You should see something like:

Casi lo tienes, crack!!!

Create a Dockerfile and run the app:

docker run ...

Call the app again:

export APP_PORT=5000
curl "localhost:${APP_PORT}"

You should see something like (🌈):

Well little papaya!!!
Version: "1.0.0"
Email: youemail
Eres un Hackermaaaaan !!!

Extra: Docker pipelines

Check the following Dockerfile.pipeline:

# Use a tar image to compress the repo
FROM ubuntu AS tar
COPY . /app/
RUN mkdir /static
RUN cd /app/ &&\
       tar -cvzf empathy-template.tar.gz * && \
        mv /app/empathy-template.tar.gz /static
# Use pandoc image to build an index.html
FROM pandoc/core AS pandoc
COPY README.md /app/README.md
COPY pandoc.css /app/pandoc.css
RUN pandoc -f markdown /app/README.md --css /app/pandoc.css -o /app/index.html --self-contained --metadata title="Dockerize"
# Copy tar and index and serve it in a nginx image
FROM bitnami/nginx:1.16.1-debian-10-r46
COPY --from=tar /static/empathy-template.tar.gz /app/empathy-template.tar.gz
COPY --from=pandoc /app/index.html /app/index.html

Go to root path:

cd ..

Build the image:

docker build -t empathyco/pipeline -f Dockerfile.pipeline .

Run the image:

docker run -p 8080:8080 -it empathyco/pipeline

Go to http://localhost:8080.

Para los putos amos!!!

Choose any language and create a Dockerfile that do the following:

Clone a repo.
Detect if has a Dockerfile.
Build the app.
Push the app to empathy/[name of the repo].
Create a html report of the email with the build status.
The end images should be minimun.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Dockerize your life

What is Docker?

Difference between VM and Container

Benefits

Docker architecture

Docker life cycle

Empathy life cycle

First steps

Docker build

Docker images

Docker run

Expose port

Docker ps

Docker inspect

Docker tag

Docker login

Docker push

Docker pull

Other images

Docker volume

Docker exec

Do it yourself

Extra: Docker pipelines

Para los putos amos!!!

About

Releases

Packages

Languages

Name		Name	Last commit message	Last commit date
Latest commit History 8 Commits
app		app
golang-app		golang-app
images		images
node-app		node-app
.gitignore		.gitignore
Dockerfile		Dockerfile
Dockerfile.pipeline		Dockerfile.pipeline
README.md		README.md
email.md		email.md
pandoc.css		pandoc.css

empathyco/platform-dockerizeyourlife

Folders and files

Latest commit

History

Repository files navigation

Dockerize your life

What is Docker?

Difference between VM and Container

Benefits

Docker architecture

Docker life cycle

Empathy life cycle

First steps

Docker build

Docker images

Docker run

Expose port

Docker ps

Docker inspect

Docker tag

Docker login

Docker push

Docker pull

Other images

Docker volume

Docker exec

Do it yourself

Extra: Docker pipelines

Para los putos amos!!!

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages