This document provides an overview of Docker and Michel Courtine's role at Docker Inc. It discusses Docker's mission to build tools for mass innovation and how Docker aims to enable a software layer to program the internet. It also highlights key Docker technologies like containers, images, and orchestration tools and how Docker is being used across various industries and platforms.
30. Traditional Architecture (pre-2000)
• One Server = One Application
• Single Stack = Single Language
• More compute = More servers
• Expensive, Slow, Inefficient
31. Virtualization (2000s)
• One Server = Multiple VMs = Multiple Stacks =
Multiple Applications
• More compute = More VMs
• 10s of VMs per Server
• Enabled Cloud Computing
32.
33. Isolation using Linux kernel features
namespaces
● pid
● mnt
● net
● uts
● ipc
● user
cgroups
● memory
● cpu
● blkio
● devices
36. docker-compose: running multiple containers
● Run your stack with one command: docker-compose up
● Describe your stack with one file: docker-compose.yml
web:
build: .
command: python app.py
ports:
- "5000:5000"
volumes:
- .:/code
links:
- redis:redis
redis:
image: redis
53. Notary
“Let’s stop using curl|sh”
Trusted collections for any content
Transport-agnostic
Reliable updates, proof of origin, resistant to untrusted
transport, survivable key compromise
Build on industry-leading standards and research
55. Engine 1.9 Release
• Network management
•Top-level docker network command
•Out of the box support for multi host overlay networking
•Extensibility through plugins
• Volume management
•Top-level docker volume command
•Extensibility through plugins
• Built-in nodes discovery
•Daemon --cluster-store and --cluster-advertise
56. Engine 1.9 Release
• Builder
•Refactoring toward client-side build support
•ARG: build-time arguments (provides support for HTTP_PROXY)
•STOPSIGNAL: choose the stop signal for the contained process
• Miscellaneous
•Quality, stability, performance improvements
•awslog logging driver
• Experimental
•User namespaces phase 1 (daemon-wide root remap)
57. Roadmap Engine 1.10
• Runtime
•Progress toward runC integration
• Distribution
•Ongoing effort to rewrite push/pull layer
•New manifest design, with content addressability from the grounds-up
• Networking
•Stabilize all the new features shipped in 1.9.0
•Better support for IPv6
• Security
•Stable user namespaces (phase 1)
79. 79
Customer Managed
Service Provider Managed
IBM SoftLayer
Bluemix started as a public PaaS
Bluemix started with a major focus on developer productivity in the public cloud.
Infrastructure as
a Service
Code
Data
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
Code
Data
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
Platform as
a Service
80. 80
Customer Managed
Service Provider Managed
IBM SoftLayer
We listened. Now we’re evolving to become even more flexible.
Capabilities in Bluemix now span PaaS and IaaS and can be delivered as a public,
dedicated, or on-premises* implementation.
Infrastructure as
a Service
Code
Data
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
Code
Data
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
Platform as
a Service
*Bluemix Local coming Summer 2015
Built on open
technologies:
81. Containers in Bluemix
Bluemix now comes with a fully integrated, high performance Docker experience, meaning monitoring,
logging, elasticity, enterprise images, and VM abstraction are all standard.
81
Docker Value IBM Value-add Customer Value
Docker Hub Registry holds a
repository of 75000+ Docker
images
• IBM hosted public registry containing IBM images - linked to
Docker Hub
• Client unique registry available on and off premises
• Enterprise-ready images
Access to the images you require to deploy
containers that meet your business needs and
strategy
Open-source, standardized,
lightweight, self sufficient LXC
container technology
• Enhanced performance with bare metal deployment
• Run images to local datacenter or cloud
• Deployment choice with pSeries & zSeries
Flexibility to choose the right hybrid cloud mix
for your business
Build, ship, and run standardized
containers
• Integrated monitoring & logging
• Elasticity to grow storage & container needs
• Life-cycle management of containers and data volumes
• No VMs to manage
Docker ease of use combined with enterprise-
level integrity and confidence
Container connections using
links and service discovery
• Private network communication
• External IP address
• Subnet Range
Extends and connects Docker containers to
production-ready enterprise environments
88. Tutum: The Container Platform
TUTUM CONTAINER PLATFORM
Any
application
Any
infrastructure
ManagedSimple Flexible
Hybrid/Agnostic
Any
Operating
System
Containers
+
Other
Design Principles:
89. Tutum: The Container Platform
Dev Deploy ManageBuild
CI CD
Code
repo
Image
repo
Monitoring
Logging
Scaling
Networking
Storage
Service Discovery
Composability
Security
Hosts Public Cloud Private CloudAcross: Environments
TUTUM CONTAINER PLATFORM
Public Cloud
Test
Orchestration
93. Docker & Microsoft
• Build
• Docker client & Kitematic for Windows
• Docker engine on Windows Server 2016 TP3
• yo-docker to dockerize existing projects
• Visual Studio integration
• Ship
• VSO?
• Run
• Azure Docker agent
• Swarm ARM template from Ahmet
• Azure Container Service
100. Stability
• Stress test under heavy load
• 100s of clients competing for the same resources
• Concurrent scheduling decisions
• Loss of hundreds of nodes while scheduler is operating