Downloaded 57 times
Uploaded byWes Eklund
Docker presentation
Docker provides a standard way to package applications into containers that are portable and can run on any infrastructure. The containers isolate applications from one another and ensure that dependencies and configurations are included so applications always run the same. This allows developers to build applications once and deploy them anywhere without worrying about compatibility or missing dependencies. It also allows operators to configure applications once and run anything on their infrastructure efficiently by eliminating inconsistencies between environments.
More Related Content
Similar to Docker presentation
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Docker presentation
- 1. Intro to Docker WesEklund LEX >> FWD
- 2. Let’s start witha problem
- 3.
- 4.
- 5.
- 6. ● 90% ofall 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’sDocker?
- 8. Application ‘Shipping’ Container Staticwebsite User DB Queue Web Service Dev VM QA Server Public Cloud Production Cluster Contributor’s laptop
- 9. Ok so whatdoes 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 worriesabout 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, RunAnything
- 14. ● Make theentire 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
- 16.
- 18.
- 19.
Editor's Notes
- #4 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
- #6 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
- #9 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
- #11 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
- #13 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
- #15 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
- #16 Aka lightweight vm Network interface Own process space Can run stuff as root At a low level it’s chroot on steriods
- #17 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
- #18 Aka lightweight vm Network interface Own process space Can run stuff as root At a low level it’s chroot on steriods