The document discusses the current status of Docker on Windows. It begins with an introduction of the presenter and then provides an overview of Windows containers and how they work using lightweight virtualization and namespaces. Examples are given of different container types and base images that can be used. The rest of the document previews a demo and discusses other Docker tools and how they work or don't currently work on Windows, with notes on where development is headed.

1. Current status of
Docker on Windows
Stefan Scherer @stefscherer
February 25 2016, Docker Meetup Bamberg
1 / 35

2. Who am I?
2 / 35

3. Who am I?
Software Engineer at SEAL Systems
3 / 35

4. Who am I?
Software Engineer at SEAL Systems
Docker chocolatey package maintainer
4 / 35

5. Who am I?
Software Engineer at SEAL Systems
Docker chocolatey package maintainer
Docker Pirate
5 / 35

6. Windows Containers
6 / 35

7. What is it all about?
7 / 35

8. What is it? A lightweight virtualization for applications
8 / 35

9. What is it? A lightweight virtualization for applications
Smaller than VM's
9 / 35

10. What is it? A lightweight virtualization for applications
Smaller than VM's
Just the files needed to run the application
10 / 35

11. What is it?
Why use it?
11 / 35

12. What is it?
Why use it?
Build - Ship - Run
12 / 35

13. What is it?
Why use it?
Build - Ship - Run
Reproducible development environment
13 / 35

14. What is it?
Why use it?
Build - Ship - Run
Reproducible development environment
Same container in dev
14 / 35

15. What is it?
Why use it?
Build - Ship - Run
Reproducible development environment
Same container in dev, test
15 / 35

16. What is it?
Why use it?
Build - Ship - Run
Reproducible development environment
Same container in dev, test and prod
16 / 35

17. What is it?
Why use it?
Build - Ship - Run
Reproducible development environment
Same container in dev, test and prod
Containers are versioned
17 / 35

18. What is it?
Why use it?
How does it
work?
18 / 35

19. What is it?
Why use it?
How does it
work?
Namespaces
File System
19 / 35

20. What is it?
Why use it?
How does it
work?
Namespaces
File System
Process IDs
20 / 35

21. What is it?
Why use it?
How does it
work?
Namespaces
File System
Process IDs
Registry
21 / 35

22. What is it?
Why use it?
How does it
work?
Namespaces
File System
Process IDs
Registry
Networking
22 / 35

23. How does it look like?
23 / 35

24. System architecture
24 / 35

25. Container types
Windows Server Containers
use same Windows kernel
lightweight, faster
Hyper-V Containers
running in Hyper-V
better isolation
docker run --isolation=hyperv
25 / 35

26. Base container images
Windows Server Core
nearly full Win32 compatible
about 9 GByte
Nano Server
fast to boot
software may need porting
about 700 MByte
FROM scratch
Base images must be preinstalled on Container Host
26 / 35

27. Demo time!
27 / 35

28. What about other Docker tools?
28 / 35

29. Swarm Works
Networking is tricky with TP4
Multi architecture swarm cluster demo at DockerCon
29 / 35

30. Swarm
Compose
Works, but ...
Networking is tricky with TP4
No links
Tried net: none
Can't wait for TP5!
30 / 35

31. Swarm
Compose
Machine
Works for Linux Docker Engines
No docker-machine create -d for TP4 at the moment
Discussion in docker/machine#2907
31 / 35

32. Swarm
Compose
Machine
Registry
Works for Windows Containers, serving from Linux
docker pull from private Registry
docker push to private Registry
32 / 35

33. Where to go next?
33 / 35

34. Try it yourself
Azure
"Deploy to azure"
Local
Windows 10 + Hyper-V
Blog post
Others
packer build
vagrant up
VirtualBox, VMware
34 / 35

35. Thank you!
Stefan Scherer
@stefscherer
github.com/StefanScherer
scherer_stefan@icloud.com
35 / 35