Introduction to Docker by Adrian Mouat
0 likes7,383 views
Docker containers provide isolated environments for applications and their dependencies, making them portable across computing environments from development to production. This allows developers to define all application dependencies in a Dockerfile to build an image, similar to a lightweight virtual machine, that can then be easily deployed on any infrastructure without configuration differences. The document discusses how Docker helps solve issues with continuous delivery, microservices architectures, and wrapping applications by making deployment faster and more consistent across environments.
Introduction to Docker by Adrian Mouat
- 2. SO WHAT IS DOCKER?
- 3. SIMILAR TO A LIGHTWEIGHT VM Both provide isolated environments Docker is much more efficient 64-bit Linux only (currently)
- 4. CONTAINERIZATION A Docker container is a portable store for a single component and its dependencies
- 5. THE SHIPPING METAPHOR Traditionally, cargo was shipped as "bulk" and "break bulk" Think sacks of coffee beans, barrels of oil etc. Lots of manual work
- 6. MEET THE INTERMODAL CONTAINER Holds goods of different shapes and sizes Shipping company doesn't care as long as it comes in a standard container Cranes, ships, forklifts, lorries all support standard containers Huge gain in efficiency
- 7. THE SOFTWARE SITUATION Modern applications have lots of components database, webserver, loadbalancer.. And lots of enivronments developer's laptop, testing VM, staging server, cloud Problems moving between them
- 8. MEET THE DOCKER CONTAINER Put anything you like in a container Database, Web server, proxy etc Ship it anywhere Use the same container in development, testing and production Provides sandboxing Isolates dependencies
- 10. ENOUGH THEORY!
- 11. DEMO TIME!
- 12. CONTAINERIZATION A Docker image is a portable store for a single component and its dependencies
- 13. DOCKER IMAGES Like a stopped VM Built from Dockerfiles List of repeatable steps Mongo Dockerfile
- 14. BUT DOCKER IS MORE THAN THIS Aims to be an "open platform" Key to this is the Docker Hub
- 16. USE CASES
- 17. CONTINUOUS DELIVERY Fast deployment pipeline Automatic testing and integration Software is always production ready Can deploy new version at "push of a button"
- 18. WHERE DOCKER COMES IN Reduces difference between dev and production Devops tool Developers define dependencies Operations concentrate on hosting containers Faster system tests
- 19. MICROSERVICES Application made up of many small independent services As opposed to monolithic applications Can easily scale and replace services Problems Deciding where to separate services Larger system (more VMs)
- 20. PREREQUISITES Rapid Provisioning Basic Monitoring Rapid Application Deployment Devops Culture http://martinfowler.com/bliki/MicroservicePrerequisites.html
- 21. WHERE DOCKER COMES IN Rapid Provisioning Good cloud support both private and public Greater efficiency means less hardware Rapid Application Deployment Much faster to spin up containers Designed to be part of a pipeline Devops Culture Docker is a DevOps tool!
- 22. WRAPPING APPLICATIONS Putting applications in container Existing desktop apps GUI and command-line For normal end users
- 23. WHY? Easy Install Safe Portable Hub for Distribution
- 24. EXAMPLES
- 26. DEVELOPMENT ENVIRONMENTS Share pre-configured set-up Plug-ins, source repositories, coding standards Also Vagrant
- 27. ERR, THIS? Fit of rage at Powerpoint Decided to try reveal.js Hard to install Node, NPM, Grunt...
- 28. CONCLUSION Containers are the future! Likely to be ubiquitous Wide range of use cases Some we haven't seen yet
- 29. Chief Scientist @ Container Solutions Writing "Using Docker" for O'Reilly @adrianmouat http://www.container-solutions.com