Download as PDF, PPTX
![#!/usr/bin/env bats # /tmp/test/nginx.bats @test "It should accept a list of UPSTREAM_SERVERS" { simulate_upstream UPSTREAM_SERVERS=localhost:4000 wait_for_nginx run curl localhost 2>/dev/null [[ "$output" =~ "Hello World!" ]] }](https://image.slidesharecdn.com/nycrb-20150811-150812174743-lva1-app6892/75/Docker-for-Ruby-Developers-59-2048.jpg)
![#!/usr/bin/env bats # /tmp/test/nginx.bats @test "It should accept a list of UPSTREAM_SERVERS" { simulate_upstream UPSTREAM_SERVERS=localhost:4000 wait_for_nginx run curl localhost 2>/dev/null [[ "$output" =~ "Hello World!" ]] }](https://image.slidesharecdn.com/nycrb-20150811-150812174743-lva1-app6892/75/Docker-for-Ruby-Developers-60-2048.jpg)
![@test "It should accept a list of UPSTREAM_SERVERS" { simulate_upstream UPSTREAM_SERVERS=localhost:4000 wait_for_nginx run curl localhost 2>/dev/null [[ "$output" =~ "Hello World!" ]] } simulate_upstream() { nc -l -p 4000 127.0.0.1 < upstream-response.txt }](https://image.slidesharecdn.com/nycrb-20150811-150812174743-lva1-app6892/75/Docker-for-Ruby-Developers-61-2048.jpg)
![#!/bin/bash # run-database.sh command="/usr/lib/postgresql/$PG_VERSION/bin/postgres -D "$DATA_DIRECTORY" -c config_file=/etc/postgresql/ $PG_VERSION/main/postgresql.conf" if [[ "$1" == "--initialize" ]]; then chown -R postgres:postgres "$DATA_DIRECTORY" su postgres <<COMMANDS /usr/lib/postgresql/$PG_VERSION/bin/initdb -D "$DATA_DIRECTORY" /etc/init.d/postgresql start psql --command "CREATE USER ${USERNAME:-aptible} WITH SUPERUSER PASSWORD '$PASSPHRASE'" psql --command "CREATE DATABASE ${DATABASE:-db}" /etc/init.d/postgresql stop COMMANDS elif [[ "$1" == "--client" ]]; then [ -z "$2" ] && echo "docker run -it aptible/postgresql --client postgresql://..." && exit psql "$2" elif [[ "$1" == "--dump" ]]; then [ -z "$2" ] && echo "docker run aptible/postgresql --dump postgresql://... > dump.psql" && exit pg_dump "$2" elif [[ "$1" == "--restore" ]]; then [ -z "$2" ] && echo "docker run -i aptible/postgresql --restore postgresql://... < dump.psql" && exit psql "$2"](https://image.slidesharecdn.com/nycrb-20150811-150812174743-lva1-app6892/75/Docker-for-Ruby-Developers-86-2048.jpg)
![#!/bin/bash # run-database.sh command="/usr/lib/postgresql/$PG_VERSION/bin/postgres -D "$DATA_DIRECTORY" -c config_file=/etc/postgresql/ $PG_VERSION/main/postgresql.conf" if [[ "$1" == "--initialize" ]]; then chown -R postgres:postgres "$DATA_DIRECTORY" su postgres <<COMMANDS /usr/lib/postgresql/$PG_VERSION/bin/initdb -D "$DATA_DIRECTORY" /etc/init.d/postgresql start psql --command "CREATE USER ${USERNAME:-aptible} WITH SUPERUSER PASSWORD '$PASSPHRASE'" psql --command "CREATE DATABASE ${DATABASE:-db}" /etc/init.d/postgresql stop COMMANDS elif [[ "$1" == "--client" ]]; then [ -z "$2" ] && echo "docker run -it aptible/postgresql --client postgresql://..." && exit psql "$2" elif [[ "$1" == "--dump" ]]; then [ -z "$2" ] && echo "docker run aptible/postgresql --dump postgresql://... > dump.psql" && exit pg_dump "$2" elif [[ "$1" == "--restore" ]]; then [ -z "$2" ] && echo "docker run -i aptible/postgresql --restore postgresql://... < dump.psql" && exit psql "$2"](https://image.slidesharecdn.com/nycrb-20150811-150812174743-lva1-app6892/75/Docker-for-Ruby-Developers-87-2048.jpg)
Uploaded byAptible
Docker for Ruby Developers
The document discusses the use of Docker for Ruby developers, highlighting its advantages over traditional virtual machines and emphasizing the importance of achieving development and production parity using Docker images and containers. It provides practical examples, including Docker commands for pulling images, running containers, and configuring services with Docker Compose, while also addressing deployment complexities in service-oriented architectures. Additionally, it touches on managing SSL infrastructure with Docker and integration testing during image builds to ensure security and reliability.
Docker for Ruby Developers
- 1. Docker for Ruby Developers NYC.rb,August 2015 Frank Macreery CTO, Aptible @fancyremarker https://speakerdeck.com/fancyremarker
- 3. Docker What’s it allabout?
- 6. Docker Containers: The newvirtual machines?
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. Getting Started with Docker Installboot2docker via http://boot2docker.io/#installation echo 'eval "$(boot2docker shellinit)"' >> ~/.bashrc
- 15. Getting Started with Docker Alternatively(if you have Homebrew and VirtualBox installed)… brew install boot2docker brew install docker
- 16. Getting Started with Docker Imagesand containers
- 17.
- 18. docker pull quay.io/aptible/nginx:latest Referenceto a Docker image
- 19. docker pull quay.io/aptible/nginx:latest Image"repositories" can have many "tags"
- 20. docker pull quay.io/aptible/nginx:latest Pullsan image from a Docker "registry"
- 21. A single Docker image consistsof many "layers"
- 22.
- 23. docker run -d-p 80:80 -p 443:443 quay.io/aptible/nginx:latest
- 24. docker run -d-p 80:80 -p 443:443 quay.io/aptible/nginx:latest Launches a new container from an existing image
- 25. docker run -d-p 80:80 -p 443:443 quay.io/aptible/nginx:latest Forward container ports to the host (host port:container port)
- 26. docker run -d-p 80:80 -p 443:443 quay.io/aptible/nginx:latest Run container in background
- 27.
- 30. Simplifying SOA Service-oriented architectureswithout the complexity
- 31.
- 33. What makes dev/prod parityso hard?
- 34. What makes dev/prod parityso hard? 1 production deployment, many development/ staging environments
- 35. What makes dev/prod parityso hard? SOA simplifies each service’s responsibilities, but often at the cost of additional deployment complexity
- 36. What makes dev/prod parityso hard? The more services you have, the harder it is to achieve dev/prod parity
- 37. What makes dev/prod parityso hard? The more engineers you have, the harder it is to standardize dev parity
- 41.
- 42. Dev/prod parity viaDocker
- 43. Dev/prod parity viaDocker Define services in terms of Docker images
- 44. # docker-compose.yml forAptible Auth/API auth: build: auth.aptible.com/ ports: "4000:4000" links: - postgresql environment: RAILS_ENV: development DATABASE_URL: postgresql://postgresql/aptible_auth_development api: build: api.aptible.com/ ports: "4001:4001" links: - redis - postgresql environment: RAILS_ENV: development DATABASE_URL: postgresql://postgresql/aptible_api_development REDIS_URL: redis://redis APTIBLE_AUTH_ROOT_URL: http://docker:4000 redis: image: quay.io/aptible/redis:latest ports: "6379:6379" postgresql: image: quay.io/aptible/postgresql:aptible-seeds ports: "5432:5432"
- 45. # docker-compose.yml forAptible Auth/API auth: build: auth.aptible.com/ ports: "4000:4000" links: - postgresql environment: RAILS_ENV: development DATABASE_URL: postgresql://postgresql/aptible_auth_development api: build: api.aptible.com/ ports: "4001:4001" links: - redis - postgresql environment: RAILS_ENV: development DATABASE_URL: postgresql://postgresql/aptible_api_development REDIS_URL: redis://redis APTIBLE_AUTH_ROOT_URL: http://docker:4000 redis: image: quay.io/aptible/redis:latest ports: "6379:6379" postgresql: image: quay.io/aptible/postgresql:aptible-seeds ports: "5432:5432"
- 46. # docker-compose.yml forAptible Auth/API auth: build: auth.aptible.com/ ports: "4000:4000" links: - postgresql environment: RAILS_ENV: development DATABASE_URL: postgresql://postgresql/aptible_auth_development api: build: api.aptible.com/ ports: "4001:4001" links: - redis - postgresql environment: RAILS_ENV: development DATABASE_URL: postgresql://postgresql/aptible_api_development REDIS_URL: redis://redis APTIBLE_AUTH_ROOT_URL: http://docker:4000 redis: image: quay.io/aptible/redis:latest ports: "6379:6379" postgresql: image: quay.io/aptible/postgresql:aptible-seeds ports: "5432:5432"
- 47. # docker-compose.yml forAptible Auth/API auth: build: auth.aptible.com/ ports: "4000:4000" links: - postgresql environment: RAILS_ENV: development DATABASE_URL: postgresql://postgresql/aptible_auth_development api: build: api.aptible.com/ ports: "4001:4001" links: - redis - postgresql environment: RAILS_ENV: development DATABASE_URL: postgresql://postgresql/aptible_api_development REDIS_URL: redis://redis APTIBLE_AUTH_ROOT_URL: http://docker:4000 redis: image: quay.io/aptible/redis:latest ports: "6379:6379" postgresql: image: quay.io/aptible/postgresql:aptible-seeds ports: "5432:5432"
- 48. Dev/prod parity viaDocker Use the same service/image configuration in production as in development (Docker Compose, Swarm, Kubernetes…)
- 49.
- 50. Elastic Load Balancer(ELB) EC2 Instance EC2 Instance NGiNX NGiNX
- 51.
- 52. How to configureNGiNX with multiple dynamic upstreams? Chef? Salt? Ansible?
- 53.
- 54. docker run -d-p 80:80 -p 443:443 -e UPSTREAM_SERVERS=docker:4000,docker:4001 quay.io/aptible/nginx:latest
- 55. docker run -d-p 80:80 -p 443:443 -e UPSTREAM_SERVERS=docker:4000,docker:4001 quay.io/aptible/nginx:latest
- 56.
- 57.
- 58. # Dockerfile # Installand configure NGiNX... # ... ADD test /tmp/test RUN bats /tmp/test https://github.com/aptible/docker-nginx Image: quay.io/aptible/nginx
- 59. #!/usr/bin/env bats # /tmp/test/nginx.bats @test"It should accept a list of UPSTREAM_SERVERS" { simulate_upstream UPSTREAM_SERVERS=localhost:4000 wait_for_nginx run curl localhost 2>/dev/null [[ "$output" =~ "Hello World!" ]] }
- 60. #!/usr/bin/env bats # /tmp/test/nginx.bats @test"It should accept a list of UPSTREAM_SERVERS" { simulate_upstream UPSTREAM_SERVERS=localhost:4000 wait_for_nginx run curl localhost 2>/dev/null [[ "$output" =~ "Hello World!" ]] }
- 61. @test "It shouldaccept a list of UPSTREAM_SERVERS" { simulate_upstream UPSTREAM_SERVERS=localhost:4000 wait_for_nginx run curl localhost 2>/dev/null [[ "$output" =~ "Hello World!" ]] } simulate_upstream() { nc -l -p 4000 127.0.0.1 < upstream-response.txt }
- 62. ENV configuration Abstracts implementationdetails: could be NGiNX, HAProxy, …
- 63. ENV configuration Simplifies configurationmanagement: central store doesn’t need to know parameters in advance
- 64.
- 65. Vulnerability Response Fix, test,docker push, restart
- 66.
- 67.
- 68.
- 69. Integration Tests Document andtest every vulnerability response
- 70. #!/usr/bin/env bats # /tmp/test/nginx.bats @test"It should pass an external Heartbleed test" { install_heartbleed wait_for_nginx Heartbleed localhost:443 uninstall_heartbleed }
- 71. @test "It shouldpass an external Heartbleed test" { install_heartbleed wait_for_nginx Heartbleed localhost:443 uninstall_heartbleed } install_heartbleed() { export GOPATH=/tmp/gocode export PATH=${PATH}:/usr/local/go/bin:${GOPATH}/bin go get github.com/FiloSottile/Heartbleed go install github.com/FiloSottile/Heartbleed }
- 72. Integration tests happen duringeach image build
- 73. Integration tests happen duringeach image build Images are built automatically via Quay Build Triggers
- 75. Integration tests happen duringeach image build Build status is easy to verify at a glance
- 77. Integration tests happen duringeach image build Quay Time Machine lets us roll back an image to any previous state
- 79. Database Deployment Standardizing an"API" across databases
- 81. New databases mean newdependencies
- 82. New databases mean newdependencies How to document setup steps for engineers?
- 83. New databases mean newdependencies How to deploy in production?
- 84. New databases mean newdependencies How to perform common admin tasks? Backups? Replication? CLI access? Read-only mode?
- 85. Wrap Databases ina Uniform API Standardizing an "API" across databases
- 86. #!/bin/bash # run-database.sh command="/usr/lib/postgresql/$PG_VERSION/bin/postgres -D"$DATA_DIRECTORY" -c config_file=/etc/postgresql/ $PG_VERSION/main/postgresql.conf" if [[ "$1" == "--initialize" ]]; then chown -R postgres:postgres "$DATA_DIRECTORY" su postgres <<COMMANDS /usr/lib/postgresql/$PG_VERSION/bin/initdb -D "$DATA_DIRECTORY" /etc/init.d/postgresql start psql --command "CREATE USER ${USERNAME:-aptible} WITH SUPERUSER PASSWORD '$PASSPHRASE'" psql --command "CREATE DATABASE ${DATABASE:-db}" /etc/init.d/postgresql stop COMMANDS elif [[ "$1" == "--client" ]]; then [ -z "$2" ] && echo "docker run -it aptible/postgresql --client postgresql://..." && exit psql "$2" elif [[ "$1" == "--dump" ]]; then [ -z "$2" ] && echo "docker run aptible/postgresql --dump postgresql://... > dump.psql" && exit pg_dump "$2" elif [[ "$1" == "--restore" ]]; then [ -z "$2" ] && echo "docker run -i aptible/postgresql --restore postgresql://... < dump.psql" && exit psql "$2"
- 87. #!/bin/bash # run-database.sh command="/usr/lib/postgresql/$PG_VERSION/bin/postgres -D"$DATA_DIRECTORY" -c config_file=/etc/postgresql/ $PG_VERSION/main/postgresql.conf" if [[ "$1" == "--initialize" ]]; then chown -R postgres:postgres "$DATA_DIRECTORY" su postgres <<COMMANDS /usr/lib/postgresql/$PG_VERSION/bin/initdb -D "$DATA_DIRECTORY" /etc/init.d/postgresql start psql --command "CREATE USER ${USERNAME:-aptible} WITH SUPERUSER PASSWORD '$PASSPHRASE'" psql --command "CREATE DATABASE ${DATABASE:-db}" /etc/init.d/postgresql stop COMMANDS elif [[ "$1" == "--client" ]]; then [ -z "$2" ] && echo "docker run -it aptible/postgresql --client postgresql://..." && exit psql "$2" elif [[ "$1" == "--dump" ]]; then [ -z "$2" ] && echo "docker run aptible/postgresql --dump postgresql://... > dump.psql" && exit pg_dump "$2" elif [[ "$1" == "--restore" ]]; then [ -z "$2" ] && echo "docker run -i aptible/postgresql --restore postgresql://... < dump.psql" && exit psql "$2"
- 88. --initialize: Initialize datadirectory --client: Start a CLI client --dump: Dump database to STDOUT --restore: Restore from dump --readonly: Start database in RO mode
- 89. db-launch () { container=$(head -c32 /dev/urandom | md5); passphrase=${PASSPHRASE:-foobar}; image="${@: -1}"; docker create --name $container $image docker run --volumes-from $container -e USERNAME=aptible -e PASSPHRASE=$passphrase -e DB=db $image --initialize docker run --volumes-from $container $@ } http://bit.ly/aptible-dblaunch
- 90. docker create --name$container $image http://bit.ly/aptible-dblaunch 1. Create "volume container"
- 91. docker run --volumes-from$container -e USERNAME=aptible -e PASSPHRASE=$passphrase -e DB=db $image --initialize http://bit.ly/aptible-dblaunch 2. Initialize database data volume
- 92. docker run --volumes-from$container $@ http://bit.ly/aptible-dblaunch 3. Run database
- 94.
- 95.