containerd and What it Means for the Container Ecosystem

Thank you Docker Meetup Sponsors!

Docker Meetup Next Month• WeneedsomeonetoorganizethemeetingforFebruary21st

• Otherwisewewillnothaveameeting• InfoSiftr TeamwillbeattheContainerWorldConference,February21st throughthe23rd attheSantaClaraConventionCenter• WewillsendoutemailinviteswithDiscountCodes

Las Vegas Docker Meetup Group is Now 300 Plus Members and Growing!

We have Docker Swagg!!!But after the Meetup

containerd Roadmap - Phase 1• GRPCAPI

• Documents:• Wearegoingfromatopdowndesignforfillingoutthismissingpiecesofcontainerd anddesignoftheAPI.

• Design• Documents:

• Thehighleveldesignworkisneededsothatthearchitectureofcontainerd staysconsistentthroughoutthedevelopmentprocess.

• Build&TestProcess• Documents:

• Weneedtohaveasimplebuildandtestprocessfornewdeveloperstobootstraptheirenvironments.Becausecontainerd willbethebaseofmanyhighlevelsystemsweneedtohaveasimplebuildprocessthatdoesnotrequirehighleveltooling.

• Status: InProgress

containerd Roadmap - Phase 2Phase2includesmostofthedesignanddevelopmentworkfortheexecutionandstoragelayersofcontainerd.Itwillincludeportingoverexisting"graphdrivers"fromDockerEngineandfindingacommonmodelforrepresentingsnapshotsforlayeredfilesystems.ThiswillalsoincludemovingtheexistingexecutioncodesupportOCI'sRuntimeSpecandtheexistingcontainerd executioncode.• Runtime

• Theruntimelayerisresponsibleforthecreationofcontainersandtheirmanagement,andsupervisionoftheprocessesinsidethosecontainers.

• Storage• Documents: https://github.com/docker/containerd/blob/master/design/snapshots.md

• Thecurrentgraphdriverswerebuiltwhenweonlyhadoverlayfilesystemslikeaufs.Weforcedthemodeltobedesignedaroundoverlayfilesystemsandthisintroducedalotofcomplexityforsnapshottinggraphdriverslikebtrfs anddevicemapper thin-p.Ourcurrentapproachistomodelourstoragelayeraftersnapshottingdriversinsteadofoverlaydriversaswecangetthesameresultsanditscleanerandmorerobusttohaveanoverlayfilesytem modelsnapshotsthanitistohaveasnapshotfilesystemmodeloverlayfilesystems.

• Status: InDesign

containerd Roadmap - Phase 3ThisphaseincludesgettingsupportfortheOCIImagespecbuiltintocontainerd.• Status: NotStarted

containerd Roadmap - Phase 4Phase4involvesgraduatingtoversion1.0,andshiftingthefocusfromfeaturestomaintenance.Graduatingto1.0implies:• Completingalloftheabovephases.• Coveringthefunctionalitiesrequiredbyamajorityofcontainer-centricplatforms.• Offeringfeatureparity,totheextentoftechnicalpossibilities,acrossLinuxandWindows.• Demonstratingthatcontainerd fulfillstherequirementsofatleastonehigher-levelplatformsthroughitscompleteintegrationasanupstream.

• Status: NotStarted

Top questions Docker, Inc. received following this announcementQ.Areyouplanningtorundocker withoutrunC ?• A.AlthoughrunC isthe default runtime,asof Docker1.12,itcanbereplacedbyanyotherOCI-compliantimplementation.DockerwillbecompliantwiththeOCIRuntimeSpecification

Q.Whatmajorchangesareontheroadmapforswarmkit torunoncontainerd ifany?• A.SwarmKit isusingDockerEnginetoorchestratetasks,andDockerEngineisalreadyusingcontainerd forcontainerexecution.Sotechnically,youarealreadyusingcontainerd whenusingSwarmKit.ThereisnoplancurrentlytohaveSwarmKit directlyorchestratecontainerd containersthough.

Top questions Docker, Inc. received following this announcement….Q.MindsharingwhyyouwentwithGRPCfortheAPI?• A.containerd isacomponentdesignedtobeembeddedinahigherlevelsystem,andserveahostlocalAPIoverasocket.GRPCenablesustofocusondesigningRPCcallsanddatastructuresinsteadofhavingtodealwithJSONserializationandHTTPerrorcodes.ThisimprovesiterationspeedwhendesigningtheAPIanddatastructures.Forhigherlevelsystemsthatembedcontainerd,suchasDockerorKubernetes,aJSON/HTTPAPImakesmoresense,allowingeasierintegration.TheDockerAPIwillnotchange,andwillcontinuetobebasedonJSON/HTTP.

Q.Howdoyouexpecttoseeothersleveragecontainerd outsideofDocker?• A.CloudmanagedcontainerservicessuchasAmazonECS,MicrosoftACS,GoogleContainerEngine,ororchestrationtoolssuchasKubernetesorMesos canleveragecontainerd astheircorecontainerruntime.containerd hasbeendesignedtobeembeddedforthatpurpose.

Top questions Docker, Inc. received following this announcement….Q.Howdidyoudecidedwhichfeatureshouldgetintocontainerd? Howdidyoucameupwiththescopeofthefuturecontainers?• A.We’retryingtocaptureincontainerd thefeaturesthatanycontainer-centricplatformwouldneed,andforwhichthere’sreasonableconsensusonthewayitshouldbeimplemented.Aspectswhichareeithernotwidelyagreedonorthatcantriviallybebuiltonelayerupwereleftout.

Q.HowintegratewithCNIandCNM?• A. Phase3ofthecontainerdroadmap involvesportingthenetworkdriversfromlibnetwork andfindingagoodmiddlegroundbetweentheCNMabstractionoflibnetwork andtheCNIspec.

Links to containerd Projectand Other Informationcontainerd LivestreamRecap• https://blog.docker.com/2017/01/containerd-livestream-recap/containerd webpage• https://containerd.ioGitHubcontainerdPage• https://github.com/docker/containerdcontainerd Roadmap• https://github.com/docker/containerd/blob/master/ROADMAP.mdSlackChannelforcontainerd• https://community.docker.com/registrations/groups/4316

Q&A and Open Discussion• Questionsaboutcontainerd• QuestionsaboutyourDocker/containerprojects• FindingsandTipsfortheGroup• GeneralOpenDiscussionabouttheecosystem