1. The document discusses Docker's roadmap which includes standardizing interfaces for container sandboxing (libcontainer), communication between containers and components (libchan), and orchestrating distributed services (libswarm). 2. It announces libcontainer becoming a standalone project and new contributors joining its development. Libchan is introduced as a lightweight communication protocol and libswarm is presented as a toolkit for composing network services. 3. Identity and authorization are mentioned as upcoming areas of focus, and the document encourages participation in developing these Docker projects.

1. Docker: the road ahead

2. So... what do we do now?
aka

3. Why are we here?

8. We have a blueprint

9. “My thought in the 70s was that the
Internet was a really good scalable
design, and we should make a
virtual internet of virtual machines
that could be cached by the
hardware machines.
It’s really too bad this didn’t happen
Alan Kay

10. Upgrade the Internet
time to

11. We have the technology
bandwidth, storage, compute, sandboxing,
crypto, compression, copy-on-write
filesystems, paxos/raft...

12. We have standard interfaces
Time to fix this!

13. It’s getting people to agree on something
The real value of Docker is not technology

14. 1. Packaging and distribution

15. 2. Sandboxing

16. libcontainer
A standard interface to OS sandboxing
namespaces, cgroups, capabilities,
netlink, selinux, apparmor
Core Docker component...
But also usable standalone

17. libcontainer
A standard interface to OS sandboxing
A few announcements.

18. libcontainer
github.com/docker/libcontainer
Now a standalone
project
#libcontainer on Freenode

19. libcontainer
Contributing SELinux and
systemd integration
Welcome Dan and Alex!

20. libcontainer
Joining as core maintainers
Welcome Victor and Rohit!

21. libcontainer
Contributing C implementation
and OpenVZ support
Welcome Pavel and John!

22. libcontainer
collaborating on unified
cgroup interface
Welcome Serge!
& LXC

23. libcontainer
Join the fun!
github.com/docker/libcontainer
#libcontainer on Freenode

24. 3.
Networking

25. libchan
a lightweight communication
protocol for distributed systems

26. libchan
Like Go channels over the network
Simple message passing
Synchronization without sharing state
Raw socket passing: channels as
gateways to any other protocol
Nesting: channels can send channels

27. libchan
Available transports:
SPDY/TLS,
websocket,
raw TCP,
high-perf unix sockets (with fd passing),
in-memory go channels.
Designed to be simple and portable

28. libchan
A standard communication layer for Docker:
internal components, plugins,
inter-container communication.

29. libchan
github.com/docker/libchan

30. 4. Orchestration

31. Docker API

33. Shipper

34. Shipper Mesosor

35. Shipper or Mesos or Coreos/FleetGeardor

36. Shipper or Mesos or Coreos/FleetGeardor
or or orConsul Helios Centurion

37. Shipper or Mesos or Coreos/FleetGeardor
or or orConsul Helios Centurion
EC2 Rackspace GCE Orchard Tutum

38. Shipper or Mesos or Coreos/FleetGeardor
or or orConsul Helios Centurion
EC2 Rackspace GCE Orchard Tutum

39. libswarm
A minimalist toolkit
to compose network services

40. libswarm
A standard interface to combine and organize
services in a distributed system.
Compose complex architectures from standard
building blocks
Avoid vendor lock-in by swapping any service out
with another
Pick services from a built-in library, or write your own
with a simple API.

41. libswarm
Community-contributed adapters:
Docker server & client
Mesos
Atomic / geard
Fleet / etcd
Orchard
Google cloud
Rackspace cloud
Tutum.com
Shipyard
TLS tunnel

42. libswarm
First-class Docker compatibility
If you develop on libswarm, we
guarantee compatibility with the
Docker ecosystem.

43. libswarm
github.com/docker/libswarm

44. libcontainer libchan
libswarm

45. What’s next?

46. 5. Identity

47. 6. Authorization

48. Coming soon!
“But I need it naow!”
Come say hi, maybe we can hook you up

50. Let’s go build it!
Happy hacking!
Drawings by @laurelcomics
#docker-dev on Freenode