Docker presentation
•Télécharger en tant que PPTX, PDF•
3 j'aime•3,505 vues
Intro to Docker for LEX >> FWD user group for June Meeting
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Docker presentation
Similaire à Docker presentation (20)
Plus de Wes Eklund
Dernier
Dernier (20)
Docker presentation
- 1. Intro to Docker Wes Eklund LEX >> FWD
- 2. Let’s start with a problem
- 4. Solution?
- 6. ● 90% of all cargo now shipped in a standard container ● Order of magnitude reduction in cost and time to load and unload ships, trains, trucks
- 7. So now what’s Docker?
- 8. Application ‘Shipping’ Container Static website User DB Queue Web Service Dev VM QA Server Public Cloud Production Cluster Contributor’s laptop
- 9. Ok so what does that give us?
- 10. ● Content Agnostic ● Hardware Agnostic ● Content Isolation and Interaction ● Automation ● Highly efficient ● Separation of duties
- 11. Developer: Build Once, Run Anywhere
- 12. ● No worries about missing dependencies, packages and other pain points during subsequent deployments ● Run each app on its own isolated container, so you can run various version of libraries and other dependencies for each app without worrying ● Automate testing, integration, packaging ● Reduce/eliminate concerns about compatibility of different platforms, either your own or your containers ● Cheap, zero penalty container to deploy services
- 13. Operator: Configure Once, Run Anything
- 14. ● Make the entire lifecycle more efficient, consistent, and repeatable ● Increase the quality of code produced by developers ● Eliminate inconsistencies between development, test, production, and customer environments ● Support segregation of duties ● Significantly improves the speed and reliability of continuous deployment and continuous integration systems ● Because the containers are so lightweight, address significant performance, costs, deployment, and portability issues normally associated with VMs
Notes de l'éditeur
- Multiplicity of goods Do I worry about how goods interact (Barrels next to Cars) Multiplicity of methods for transporting/storing Can I transport quickly and smoothly
- A standard container that is loaded with virtually any goods, and stays sealed until it reached final delivery In between can be loaded and unloaded, stacked, transported efficiently over long distances And transferred from one mode of transport to another
- Multiplicity of stacks Do services and apps interact appropriately An engine that enables any payload to be encapsulated as a lightweight, portable self serving box That can be manipulated using standard operations and run consistently on virtually any hardware platform Multiplicity of hardware environments Can I migrate smoothly and quickly Developer: Build Once, Run Anywhere Operator: Configure Once, Run Anything
- Can encapsulate any payload and its dependencies Using OS primitives can run consistently on virtually any hardware - VMs, bare metal, open stack, public IAAS - without modification Resource, network, and content isolation - avoids dependency hell Standard operations to run, start, stop, commit, search: Perfect for devops: CI, CD, autoscaling, hybrid clouds Lightweight, virtually no perf or startup penalty, quick to move and manipulate Developer worries about code, ops worries about infrastructure
- Can encapsulate any payload and its dependencies Using OS primitives can run consistently on virtually any hardware - VMs, bare metal, open stack, public IAAS - without modification Resource, network, and content isolation - avoids dependency hell Standard operations to run, start, stop, commit, search: Perfect for devops: CI, CD, autoscaling, hybrid clouds Lightweight, virtually no perf or startup penalty, quick to move and manipulate Developer worries about code, ops worries about infrastructure
- Can encapsulate any payload and its dependencies Using OS primitives can run consistently on virtually any hardware - VMs, bare metal, open stack, public IAAS - without modification Resource, network, and content isolation - avoids dependency hell Standard operations to run, start, stop, commit, search: Perfect for devops: CI, CD, autoscaling, hybrid clouds Lightweight, virtually no perf or startup penalty, quick to move and manipulate Developer worries about code, ops worries about infrastructure
- Aka lightweight vm Network interface Own process space Can run stuff as root At a low level it’s chroot on steriods
- Can encapsulate any payload and its dependencies Using OS primitives can run consistently on virtually any hardware - VMs, bare metal, open stack, public IAAS - without modification Resource, network, and content isolation - avoids dependency hell Standard operations to run, start, stop, commit, search: Perfect for devops: CI, CD, autoscaling, hybrid clouds Lightweight, virtually no perf or startup penalty, quick to move and manipulate Developer worries about code, ops worries about infrastructure
- Aka lightweight vm Network interface Own process space Can run stuff as root At a low level it’s chroot on steriods