The document outlines the agenda for the Global Hack Day #3, including rules, timeline, and prize categories focused on Docker projects. Participants can work in teams of 1-3 from September 16th to September 21st, with prizes for the top three teams in each category. The document also discusses enhancing the developer toolbox and infrastructure plumbing, detailing tools like runc and Docker Notary.

2. Agenda
• Global Hack Day #3: Rules, Timeline, Prizes
• OSS Product Updates & Demos
• Getting involved

3. Rules
• Team of 1-3 hackers
• From 4pm PDT on Wednesday, September 16th,
to 9am PDT on Monday, September 21st
• Theme: Hack on a project using Docker or its infrastructure
plumbing (runC, Notary) as a central piece.
Categories:
1. Docker Plugins
2. Docker Plumbing – runC, Notary, etc.
3. Docker Freestyle –using / improving features from the latest Docker
releases including Engine and other Docker OSS projects

4. Timeline
Kick Off
&
Livestream!
Hack! Hack! Hack!
Hack!
Submission
Deadline &
Local Winners

5. Prizes
• 1st Place Global Winners: Each member of the three winning
teams (one for each category) will receive a complimentary pass for
DockerCon Europe + accommodations + a lightning talk
• 2nd Place Global Winners: Each member of the three 2nd place
winning teams (one for each category) will receive a limited edition
Docker hoodie.
• 3rd Place Global Winners: Each member of the 3rd place winning
teams (one for each category) will receive a Docker-customized Tile.
• Local Edition Winners: Each member of the winning local edition
team will win a special edition Docker baseball shirt.

6. Building Tools of Mass Innovation

8. Mass innovation
Mass innovation

9. The Docker Mission
9
Anywhere
Distributed Applications
Build Ship Run
Build tools of mass innovation so you can…

10. 10
1. Promote Open Standards
3. Reinvent the Developer Toolbox
2. Improve Infrastructure
Plumbing
4. Unique solutions to business
problems
To do that, we need

11. Promote Open Standards
11

12. Open Container Initiative (OCI)
Industry leaders join forces to eliminate fragmentation
• Form a vendor-neutral, open source governance under Linux Foundation
• Establish common standards for container format and runtime
• Docker donated its runtime and associated specifications
• Appointed x-industry maintainers from the libcontainer project
12
http://www.opencontainers.org/

13. Improve Infrastructure Plumbing
13

14. Improve Infrastructure Plumbing
Principles of Software Plumbing
• Re-use and improve existing plumbing
• Make new plumbing easy to re-use and improve
• Make small and simple tools, not big complicated ones
• Define standard interfaces for assembling larger systems
50% of Docker source code is plumbing
14

15. Introducing RunC
Universal runtime for OS containers
• Supports all security features of Linux: selinux,
apparmor, cgroups, seccomp, cap-drop..
• Supports user namespaces, container migration
• Microsoft is contributing Windows support
• Arm support underway
• Intel is contributing DPDK, Secure enclave
• Defines a standard, portable runnable format
• Usable from the command-line or programmatically
https://runc.io
15

16. Introducing Docker Notary
• Trusted cross platform content distribution
• Platform-agnostic to distribute any content
• Trusted client – server interaction
• Publisher signed content
• Publisher key validates integrity of content
https://github.com/docker/notary
16

17. runC Demo by Michael Crosby

18. Docker Content Trust Demo
By Nathan McCauley
18

19. Re-Invent the Developer Toolbox
19

20. Networking
Orchestration
Plugins
20
Docker Platform

21. Networking
Transform Networking as Docker Transformed Compute
• Distributed application portability
• For Devs: SDN for Docker containers
– Re-architected network stack with libnetwork
– Consistent dev experience with Docker CLI
– Multi-container networking
• For Ops: Operator defined and managed network infrastructure
– Multi-host networking
– Plug in support from range of providers
21

22. Plugins
Pluggable Architecture to extend Docker functionality
• Introducing Networking and Volume plugins
• For Users: Portability and choice for developers and ops
• For Partners: Easily integrate and access Docker users
• Collaboration with Cluster HQ, Glider Labs, Weave
22
Docker Engine
Plugins
docker
Docker client
Volumes
Networking
Service Discovery
Scheduling
Coming soon!

23. Orchestration Across the App Lifecycle
Docker Machine
Docker Swarm
Docker Compose
23

24. Swarm + Machine + Compose
Docker
CLICompose
Compose
Machine
.yml Description
up / scale / stop/ kill / rm
create / destroy

25. Networking / Plugins Demo by David Calavera
25

26. Orchestration Status Update by Jérôme Petazzoni
26

27. Keeping up with Docker Machine
• Libmachine is happening!
(PR#1729)
• Disk access is moving to the persist module
• Drivers are moving to plugins
• See nathanleclaire/moby for a sample app
(define your machines with a YAML file)
• Overall stability and usability fixes
(in particular with VirtualBox experience)
27

28. Keeping up with Docker Compose
• Parallel operations
(so that "docker-compose up" is faster)
• Better integration with Swarm
• Windows support
• Better "extends" mechanism
• Hack ideas: issues #1510 #1953
28

29. Keeping up with Docker Swarm
• Better integration with Engine (PR#16229)
(easier discovery → easier cluster deployment)
• New discovery mechanism
(peer-to-peer, based on Serf)
29

30. Getting involved
• Submit hack ideas or reach out to people who
have already submitted their ideas to find
team mates & form a team
• Attend local editions or participate remotely
• Join the conversation on twitter
#dockerhackday

31. Submission process
• Step 1: Go to github.com/docker/global-hack-day-3/
• Step 2: Fork the repository, and create a subdirectory titled with the name
of your team.
• Step 3: Start hacking on the best Docker project you can think of for a
chance to win the Docker Global hack Day #3!
• Step 4: Once your hack is ready, submit a pull request to this repository
before 9am PDT on Monday, September 21st. All files related to your hack
should live inside your team's subdirectory.
• Step 5: Once you've submitted your Pull Request, go ahead and submit
additional infos about your hackday project via the form on
Docker.com/community/hackathon

32. Thank you sponsors

34. *
*Ceci n’est pas une pipe

35. *
*Ceci n’est pas une pipe