Boston Code Dojo - Docker meetup slides
0 likes592 views
The document discusses development environments using Docker containers. It notes that Docker can simplify collaboration by eliminating dependency issues and allowing for reusable, distributable images. Docker provides fast builds through caching and composability through linking and sharing data between containers. An example dev environment is provided that builds an API image with different branches. Challenges are posed around breaking projects into containerized pieces and sharing code between containers and hosts to enable live reloading as code changes.
Boston Code Dojo - Docker meetup slides
- 2. Disclaimer I do this to learn, not to teach. Wednesday, July 8, 15
- 3. No Dependency Hell (Other than Docker itself) Motivation: simplify collaboration in developer teams, especially distributed teams with no standardized software Wednesday, July 8, 15
- 4. Easy distribution • Docker is all about reusability • You can find tons of prebuilt images at Docker registry • You can upload and distribute your own images at Docker hub, or host your own private registry Wednesday, July 8, 15
- 5. Fast builds • Docker images are cached locally • You can build on top of existing images • Caching is incremental (each command in your Dockerfile gets cached) Wednesday, July 8, 15
- 6. Composability • Docker Compose (formerly fig) lets you orchestrate containers with shared data • Containers, as well as the host OS, can share data via VOLUMES • Links allow a container to access another container’s ENV and exposed ports Wednesday, July 8, 15
- 7. Dev environment example •http://bit.ly/1NSJo51 •Master branch builds the API image •api-from-image branch uses an image I created •Example app: http://bit.ly/1dMcCFG Wednesday, July 8, 15
- 8. Useful Start boot2docker and export environment variables: boot2docker init && $(boot2docker up | grep "export") Figure out what host your containers are running on: boot2docker ip Push a running container as an image: docker commit -m COMMIT_MESSAGE CONTAINER_ID IMAGE_TAG docker push IMAGE_TAG Start a shell in a running container (busybox sh, /bin/bash, etc.): docker exec -it CONTAINER_ID SHELL_COMMAND Wednesday, July 8, 15
- 9. Useful Forward ports from boot2docker to your host OS: boot2docker ssh -vnNTL PORT:localhost:PORT View all running containers started with compose: docker-compose ps View log entries for a particular container: docker ps CONTAINER_ID View logs for a particular container: docker logs CONTAINER_ID Wednesday, July 8, 15
- 10. Challenge Wednesday, July 8, 15
- 11. • Pick a project and think about how to break it up into pieces (one process - or near it, per container) • Keep your Docker config and your code separated • Allow for sharing of your code between your host OS and the Docker container Wednesday, July 8, 15
- 12. • If your code changes, restart your server (live reload) • Allow for using git, either from the container or from the host OS • The purpose here is to create a truly distributable development environment Wednesday, July 8, 15