Rubyslava #66 (container edition)
Download as PPTX, PDF0 likes142 views
The document discusses different strategies for building and running Docker containers. It outlines approaches for building simple versus advanced container images, including packaging development dependencies. It also describes options for running containers such as using docker run commands, docker-compose, swarm mode, or orchestration tools. Tips are provided such as building ephemeral containers, using multiple compose files for different environments, and initializing databases for tests.
Rubyslava #66 (container edition)
- 1. Build - ship - Run approaches & strategies Adam Štipák | @new_POPE | adam.stipak@gmail.com
- 2. Build - basics should be “ephemeral” use .dockerignore unnecessary packages only one concern https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/ number of layers multi-line arguments cache
- 3. Build - simple version all in one for simple projects
- 4. Build - advanced version one image per service build & dev dependencies (extra image?) cache (composer, npm, yarn, gem, etc.) push & pull
- 5. Build - my tips strategy depends by project all in one (e.g. nginx + php-fpm, from official image, from scratch) dev dependencies packed in image option to enable/disable it don’t use standalone dev & prod image development (test) image “extend” production image
- 6. Run - options 1. docker run … 2. docker-compose up & run 3. swarm mode 4. portainer.io, kubernetes.io, EC2 Container Service, etc.
- 7. Run - docker run ... examples & tutorials library development (cd myproject && docker run -v $(pwd):/src php7.1) all in one image
- 8. Run - docker-compose up & run development vs. test, stage (CI) vs. production issues more compose files -f base.yml -f dev.yml extends (removed in docker compose v3) standalone (docker-compose.dev.yml, ...test.yml, ...prod.yml)
- 9. Run - my tips using only docker-compose for run except kubernetes, portainer, ... compose file per environment database init for tests
- 10. Thank you! Adam Štipák | @new_POPE | adam.stipak@gmail.com