Docker - a lot changed in a year
Download as PPT, PDF0 likes792 views
Docker has developed rapidly in the past year. It started as a simple tool used to package applications into containers using LXC but has since replaced LXC with its own containerization technology. Major releases introduced compatibility with mainstream Linux distributions, a regular release cycle, and production support. The ecosystem around Docker is also expanding rapidly with new tools for container orchestration, composition, and platforms as a service being built using Docker. While Docker has come a long way, there is still work to be done in areas like security and managing container lifecycles and dependencies.
Docker - a lot changed in a year
- 1. copyright 2014 1 Docker: A lot changed in a year Chris Swan, CTO @cpswan Cloud native networking
- 2. copyright 2014 2 TL;DR Docker is important for DevOps because it tightens iteration loops The core project developed very fast, but the ecosystem is now moving faster They did it with Docker
- 3. copyright 2014 3 Why me?
- 4. copyright 2014 Grid, Cloud, Docker 4
- 6. copyright 2014 6 This is a DevOps track, so why do we care about Docker?
- 7. copyright 2014 John Boyd’s OODA loop
- 8. copyright 2014 8 In the beginning
- 9. copyright 2014 0.1.0 (2013-03-23) Used LXC Registry to push/pull images 9
- 10. copyright 2014 10 Where were we a year ago?
- 11. copyright 2014 0.6.6 (2013-11-06) Runtime •Ensure container name on register •Fix regression in /etc/hosts •Add lock around write operations in graph •Check if port is valid •Fix restart runtime error with ghost container networking •Add some more colors and animals to increase the pool of generated names •Fix issues in docker inspect •Escape apparmor confinement •Set environment variables using a file. •Prevent docker insert to erase something •Prevent DNS server conflicts in CreateBridgeIface •Validate bind mounts on the server side •Use parent image config in docker build •Fix regression in /etc/hosts 11 Client •Add -P flag to publish all exposed ports •Add -notrunc and -q flags to docker history •Fix docker commit, tag and import usage •Add stars, trusted builds and library flags in docker search •Fix docker logs with tty RemoteAPI •Make /events API send headers immediately •Do not split last column docker top •Add size to history Other •Contrib: Desktop integration. Firefox usecase. •Dockerfile: bump to go1.2rc3
- 12. copyright 2014 We still didn’t have • A regular release cycle • Compatibility with standard Linux distros • Links • Naming Much of that came in 0.7.0 towards the end of Nov 2013 12
- 13. copyright 2014 13 The watershed release
- 14. copyright 2014 0.9.0 (2014-03-10) Libcontainer (LXC gets thrown under the bus) 14
- 15. copyright 2014 0.9.1 (2014-03-24) Ubuntu 14.04 Centos 7 Etc. 15
- 16. copyright 2014 16 And then came DockerCon
- 17. copyright 2014 1.0.0 (2014-06-09) Notable features since 0.12.0 (2014-06-05) •Production support 17
- 22. copyright 2014 22 Shocker, Flocker, Clocker
- 23. copyright 2014 Shocker 23 The issue The response http://stealth.openwall.net/xSports/shocker.c https://news.ycombinator.com/item?id=7910117
- 30. copyright 2014 30 PaaS caught Docker
- 31. copyright 2014 Docker based PaaS 31
- 32. copyright 2014 Docker in PaaS 32
- 33. copyright 2014 PaaS == Opinionated? 33
- 34. copyright 2014 Docker might be the anti PaaS 34
- 35. copyright 2014 PaaS == Operationalised? 35
- 37. copyright 2014 Everybody has one… 37
- 38. copyright 2014 Kubernetes is the one to watch 38
- 40. copyright 2014 … not containerised cloud (yet) 40
- 41. copyright 2014 41 So why does it matter?
- 42. copyright 2014 Build, Ship > Run? 42 Image credit http://www.mediaagility.com/2014/docker-the-next-big-thing-on-cloud/
- 43. copyright 2014 Docker Hub 43 Image credit http://blog.docker.com/2014/06/announcing-docker-hub-and-official-repositories/
- 44. copyright 2014 Bottled software 44 Image credit CC Julio Morales https://www.flickr.com/photos/phooleo/4703216251
- 45. copyright 2014 45 There’s still a bunch of work to be done
- 46. copyright 2014 Containers don’t contain 46 With thanks to Dan Walsh @rhatdan Watch his DockerCon 2014 presentation at http://is.gd/dcrhdw
- 47. copyright 2014 47 The manifest problem
- 48. copyright 2014 Each active line creates a layer 48 Base OS Sources Update repos Install nginx Mod nginx.conf Mod index.html
- 49. copyright 2014 An image binds layers together 49 Base OS Sources Update repos Install nginx Mod nginx.conf Mod index.html
- 50. copyright 2014 Nginx example The image is the unit of deployment 50
- 51. copyright 2014 Nginx example What version of nginx is that? 51
- 52. copyright 2014 Nginx example What version of OpenSSL installed? 52 ?
- 53. copyright 2014 Nginx example and which bash? 53 ?
- 54. copyright 2014 54 My Docker wish list
- 55. copyright 2014 Feb 2014 Docker CLI Disk quotas Route propogation 55
- 56. copyright 2014 Nov 2014 Docker CLI Disk quotas Finer life cycle control 56
- 57. copyright 2014 If you want a better Docker Learn Go 57
- 58. copyright 2014 58 And another thing…
- 60. copyright 2014 Governance 1. Mature tooling/CI process so project can scale (more) 2. Dealing with long outstanding pull requests 3. Clear separation between Docker the company and Docker the project (and clarification of MS relationship) 4. Clear articulation of roadmap 60
- 62. copyright 2014 62 How did we come so far so fast?
- 63. copyright 2014 They used Docker 63
- 64. copyright 2014 64 Wrapping up
- 65. copyright 2014 65 TL;DR Docker is important for DevOps because it tightens iteration loops The core project developed very fast, but the ecosystem is now moving faster They did it with Docker
- 66. copyright 2014 66 Chicago, US ContactMe@cohesiveft.com +1 888 444 3962 Questions?
Editor's Notes
- #5: Before we had clouds we had grid – I built a large compute grid for a big Swiss bank I’ve been using the cloud since its inception, and the company I work for helps customers build networks in the cloud We decided last summer to put Docker into our product. So I’ve been paying close attention to the development of Docker and its ecosystem
- #23: Containers and PaaS often go together, but is this really want people want
- #27: Containers and PaaS often go together, but is this really want people want
- #31: Containers and PaaS often go together, but is this really want people want
- #32: A bunch of people have made platform as a service based on Docker
- #33: Decker was perhaps the first project to bring Docker to Cloud Foundry But now we also have Diego (DEA Go) – so there’s a choice of ways that you can run Docker containers And Apcera Continuum, which comes from Cloud Foundry creator Derek Collison, has also adapted to run Docker containers
- #34: PaaS has forced language choice PaaS has forced framework choice PaaS leaves developers with less choice Sometimes that’s a good thing – get away from analysis paralysis
- #35: No opinion Full choice on language Any framework It’s just Linux. Your Linux. However you want it
- #36: Will a Docker PaaS be about ops rather than dev? Logging Monitoring Scaling
- #37: Maybe we don’t really need a PaaS for operational needs – perhaps orchestration is enough
- #38: So we have Mesos (from Twitter) and Kubernetes (from Google) and Tupperware (from Facebook)
- #39: Obviously Kubernetes runs on Google’s own cloud platform But IBM and Microsoft have also launched services that build on it This is Google using open source as a competitive weapon against Amazon – redefining cloud as container based rather than VMs Google’s experience with containers and fungability of infrastructure makes them best placed to be winners in the containerised cloud
- #42: Maybe we don’t really need a PaaS for operational needs – perhaps orchestration is enough
- #43: Many fixate on Docker’s use of containers, but that’s only the ‘run’ part of the story. Dockerfile gives us a tool to build containers We can then move around the Dockerfile, or the image that we get from the Dockerfile
- #44: Docker Hub gives us a place where we can find useful containers These can be the basis for new containers that we build
- #45: Brewing is a great craft, but we don’t always want to make beer and wait weeks for the results If you just want to drink beer then let somebody else do the hard work The same thing is happening with software – I can go to Docker Hub and get bottled software By the way… Pliny the Elder is the best – seek it out