Introduction to Docker at PHPBenelux2015

INTRODUCTION TO DOCKER WORKSHOP, PHPBENELUX2015

ANDREAS HUCKS Software Architect at SensioLabs DE @meandmymonkey

WHAT TO COPY FROM USB DRIVES • Only copy /boxes
if you didn't download them already • Only copy /installers if you don't have Vagrant and/or Virtualbox • … and even then only the necessary files

$ vagrant box add -‐-‐name phpbnl15-‐services \ /path/to/phpbnl15-‐services.box
  $ vagrant box add -‐-‐name phpbnl15-‐playground \ /path/to/phpbnl15-‐playground.box SETUP: VAGRANT BOXES

$ cd /path/to/vagrantfile $ vagrant up $ vagrant
ssh playground SETUP: SPIN UP VAGRANT & CONNECT

$ pwd /home/vagrant $ whoami vagrant
$ lsb_release -‐a Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty ENVIRONMENT

SOFTWARE DEVELOPMENT IS ABOUT BREAKING PROBLEMS INTO SMALLER PIECES

WHAT ARE (DOCKER) CONTAINERS? • Linux Containers • Have been
around for some years • They are not VMs • Use the same kernel

WHAT ARE (DOCKER) CONTAINERS? • Kernel Namespaces • cgroups •
See https:/ /linuxcontainers.org/

WHAT ARE (DOCKER) CONTAINERS? • Docker creates a simple API
for all of this • Written in Go • Provides a CLI and a RESTlike API

RUNNING DOCKER • Kernel 3.8 or above • Union Filesystem
support • Cgroups and namespaces enabled • This means no OSX (yet) • Although there is boot2docker

WHY RUN DOCKER? • Fast, disposable development environments • Easy
deployment of applications • Testing and integrations tasks

WHY RUN DOCKER? • Microservice architectures • Scaling applications •
DIY PaaS • … although this will not fit into today's schedule ;)

BUT WHAT ABOUT PUPPET|ANSIBLE|CHEF|SALT? • Docker does not replace configuration
management tools • These tools can in fact be used to provision docker platforms and/or containers themselves

CONTAINER GOTCHAS • Not a VM! • There is no
init process, *your* process is PID 1 instead • Security implications, isolation is not complete • No reaping, no cron, no services • Zombies!

NODE (PID 1) SOMESCRIPT (PID 2) SOMETOOL (PID 3)

NODE (PID 1) SOMETOOL (PID 3)

NODE (PID 1) SOMETOOL (PID 3) Brraaainns.

$ docker run \ registry.dockerworkshop.dev/ubuntu:14.04 \
echo "Hello World" HELLO WORLD

WHAT HAPPENED? • Docker downloaded an image from a registry
• Docker ran our command • It quit (this is important)

$ docker run \ registry.dockerworkshop.dev/ubuntu:14.04 \
/bin/bash INSIDE THE CONTAINER

$ docker run -‐ti \ registry.dockerworkshop.dev/ubuntu:14.04 \
/bin/bash OOPS, SECOND TRY

$ docker images $ docker images -‐a LIST DOCKER
IMAGES

HANDS ON • Spin up an Ubuntu Container • Install
Nginx* • Exit * echo "daemon off;" >> /etc/nginx/nginx.conf

$ docker ps -‐a $ docker commit [hash] myfirstcontainer
$ docker run myfirstcontainer nginx WHAT NOW?

$ docker run -‐d -‐p 8080:80 myfirstcontainer nginx $
docker ps $ curl localhost:8080 PROPERLY DETACH AND CONNECT

$ docker exec nginx ps -‐aux A SNEAK PEEK INSIDE

$ docker ps $ docker stop [name|tag] $
docker rm [name|tag] $ docker rm -‐f [name|tag] CLEAN UP

$ docker tag myfirstcontainer \ registry.dockerworkshop.dev/myfirstcontainer $
docker push \ registry.dockerworkshop.dev/myfirstcontainer PROPERLY TAG & PUSH THE CONTAINER

$ docker search registry.dockerworkshop.dev/nginx $ docker search registry.dockerworkshop.dev/ubu PROPERLY
TAG & PUSH THE CONTAINER

$ curl registry.dockerworkshop.dev/v1/search?q=ubu | jq . $ curl registry.dockerworkshop.dev/v1/search
| jq . $ curl \ registry.dockerworkshop.dev/v1/repositories/ubuntu/tags \ | jq . ADVANCED: REGISTRY JSON API

SHOULDN'T THIS BE AUTOMATED? • It's called Dockerfile • Defines
all build steps • Build and tag (not push) in a single command • Cache results to speed up consecutive builds

FROM ubuntu:14.04 RUN apt-‐get -‐y install python-‐pip RUN
apt-‐get -‐y install python-‐dev liblzma-‐dev […] ADD . /docker-‐registry ADD ./config/boto.cfg /etc/boto.cfg RUN pip install /docker-‐registry/depends/docker-‐ registry-‐core […] EXPOSE 5000 CMD exec docker-‐registry DOCKERFILE (Excerpt from Dockerfile for Docker Registry)

docker build [OPTIONS] PATH -‐-‐force-‐rm=false
Remove intermediate containers -‐-‐no-‐cache=false Do not use cache when building -‐q, -‐-‐quiet=false Suppress verbose output -‐-‐rm=true Remove intermediate containers -‐t, -‐-‐tag="" Repository name and tag DOCKERFILE

$ docker build \ -‐t registry.dockerworkshop.dev/nginx:phpbnl15 ./ DOCKERFILE

HANDS ON • Write a Dockerfile for a Nginx container
• Build and push it • You may check the cheat folder for "nginx" to save some typing

server {
[…] access_log /dev/stdout; $ docker logs -‐f nginx LOGGING

USE CASE: TESTING

HANDS ON • We need a container running PHP-CLI •
For simplicity, a global phpunit.phar install • We need a workdir to define where we will run our tests later • Tag as registry.dockerworkshop.dev/ phpunit:php55

$ docker run -‐rm \ registry.dockerworkshop.dev/phpunit:php55 phpunit EXECUTE

HANDS ON • Build another phpunit container • This time,
running PHP 5.3.x • (Yes, 5.3) • Hint: There is a ubuntu:12.04 in the registry • Tag as registry.dockerworkshop.dev/ phpunit:php53

$ docker run -‐rm \ registry.dockerworkshop.dev/phpunit:php53 phpunit EXECUTE

NICE, BUT… • Isolated, throw-away testing environments! • We still
have a dedicated config on the CI side, because it needs to know about specifics (like the container names)

INTRODUCING FUGU • Written in Go • Utility to preconfigure
docker run & build commands • For single containers • A single, simple YAML file • Allows us to configure our tests a bit similar to Travis (right in our project)

fugu <command> [fugufile] \ [label]
[docker-‐options] [command] [args...] commands: run wraps docker run build wraps docker build FUGU

# fugu.yml default: image: dockerfile/nginx
name: hello-‐world-‐nginx detach: true publish: -‐ 8080:80 volume: -‐ /host/path:/container/path […] FUGUFILE

# fugu.yml default: image: registry.dockerworkshop.dev/myfirstcontainer
command: nginx name: fugutest detach: true publish: -‐ 8080:80 EXAMPLE: OUR FIRST CONTAINER

HANDS ON • Add a fugu.yml to our PHP Project
• Use two labels to run both PHP Versions • Result: • $ fugu run php55 • $ fugu run php53

IDEAS • Build a complete single container with DB and
fixtures and run Behat • Build separate DB containers with different fixtures • If a test fails, push the resulting container to a registry for further analysis • …

DOCKERIZING A WEB APP

REQUIREMENTS • Extend our Nginx container with PHP-FPM • Build
a separate MySQL container • Connect them somehow

HANDS ON: PHP • Base: our Nginx container • Install
PHP Packages and supervisord • Download and install composer • Replace webroot, Nginx config, index.html • Set CMD to supervisor • Tag and push

$ docker run -‐d -‐P -‐-‐name php5 \
-‐v /home/vagrant/docker-‐workshop-‐app/:/var/www/ \ registry.dockerworkshop.dev/php5 PHP

HANDS ON: MYSQL • Cheat: we use the official MySQL
Dockerfile ;) • Try to add DB creation, see SQL in web application root • Tag and push

$ docker run -‐d -‐P -‐-‐name mysql \
registry.dockerworkshop.dev/mysql MYSQL

CONNECTING • The PHP container needs to now where to
find the DB • Solution: Links • Create environment variables with network info • Add entries to /etc/hosts

$ docker run -‐d -‐P -‐-‐name php5 —link mysql:mysql \
-‐v /home/vagrant/docker-‐workshop-‐app/:/var/www/ \ registry.dockerworkshop.dev/php5 PHP

HANDS ON • Run the PHP container interactively and check
out the /etc/hosts file • Modify the database connection code in src/app.php line 27 to use the new hostname

# fig.yml web: build: .
command: python app.py links: -‐ db ports: -‐ "8000:8000" db: image: postgres FIG

THANKS! Please give feedback: https:/ /joind.in/13101

Introduction to Docker at PHPBenelux2015

Introduction to Docker at PHPBenelux2015

More Decks by Andreas Hucks

Other Decks in Programming

Featured

Transcript