Introduction to Docker
5 likes1,329 views
This document provides an introduction to Docker, describing it as a way to build, ship, and run applications using containers. It discusses how Docker allows building applications once that can run anywhere, isolated and layered for portability and efficiency. Key benefits outlined include clean and portable applications, efficient operations, and support for continuous integration and deployment workflows.
![Building Docker images
FROM ubuntu
MAINTAINER James Turnbull "james@example.com"
RUN apt-get -qqy update
RUN apt-get install -qqy apache2
ADD index.html /var/www/
ENV APACHE_RUN_USER www-data
ENV APACHE_RUN_GROUP www-data
ENV APACHE_LOG_DIR /var/log/apache2
VOLUME [ "/var/log/apache2" ]
EXPOSE 80
ENTRYPOINT ["/usr/sbin/apache2"]
CMD ["-D", "FOREGROUND"]
23](https://image.slidesharecdn.com/intro-141108045549-conversion-gate02/85/Introduction-to-Docker-23-320.jpg)
Introduction to Docker
- 1. Introduction to Docker Containerization is the new virtualization James Turnbull @kartar 1
- 2. who • VP of Engineering at Kickstarter • Advisor at Docker • Open source chap • Funny accent 2
- 3. Kickstarter live in Sweden 3
- 4. The Docker Book www.dockerbook.com 4
- 5. Who are you folks? 5
- 6. What's this all about? 6
- 7. What is Docker? 7
- 9. Build, ship, run 9
- 10. Build once 10
- 11. Run in many places 11
- 12. Isolated Layered Standard Content agnostic 12
- 13. But this isn't new?!? 13
- 14. So why should I care? Software delivery mechanism Portability A bit like a VM but ... 14
- 15. ... not like a VM 1. Containers boot faster 2. Containers have less overhead 3. Containers bring native performance 4. Containers are Cloud & VM-compatible 15
- 16. Devs care about their app Ops cares about the containers 16
- 17. Why developers care... • Clean, safe, hygienic and portable • No worries about dependencies • Encourage good architecture 17
- 18. Why operations care... • Make the lifecycle more efficient • Eliminate inconsistencies • Support segregation of duties 18
- 19. What can I use Docker for? • Docker for CI/CD • Packaging and deploying applications • Build your own PAAS • Deploy applications at hyperscale! 19
- 20. Does this work with Puppet or Chef? • Chef and Puppet are state management tools • Less complex • Docker images are version controlled and layered • Smaller, self-contained and lightweight 20
- 21. Technology Stack • Runs on most Linux distros • Boot2Docker for OSX and Windows • Windows in the works! • Uses Linux kernel features 21
- 22. Docker Basics Image & Dockerfile The Docker Hub Container 22
- 23. Building Docker images FROM ubuntu MAINTAINER James Turnbull "james@example.com" RUN apt-get -qqy update RUN apt-get install -qqy apache2 ADD index.html /var/www/ ENV APACHE_RUN_USER www-data ENV APACHE_RUN_GROUP www-data ENV APACHE_LOG_DIR /var/log/apache2 VOLUME [ "/var/log/apache2" ] EXPOSE 80 ENTRYPOINT ["/usr/sbin/apache2"] CMD ["-D", "FOREGROUND"] 23
- 24. Building the image $ sudo docker build -t="jamtur01/0redev" . 24
- 25. Sharing the image $ sudo docker push jamtur01/0redev 25
- 26. Running the container $ sudo docker run --name mywebsite -ti -p 80:80 jamtur01/0redev 26
- 27. But there's more! 27
- 28. What if we could componentize . . . 28
- 29. SSH 29
- 30. Managing a container $ sudo docker exec -ti mywebsite /bin/bash 30
- 31. Scheduling and jobs 31
- 32. Logging 32
- 33. Logging container $ sudo docker run --volumes-from mywebsite -ti ubuntu tail -f /var/log/apache2/acccess.log 33
- 34. Creates a new architecture 34
- 35. A new architecture that ... • Separates orthogonal concerns • Don't rebuild your app to change services • Have different policies in domains • Ship lighter apps 35
- 36. Questions? 36