short-lived. If a container reboots, the data inside it is lost; hence, the introduction of Docker volumes. Docker volumes lack a defined lifecycle like the containers (as of this publish date). In contrast architecture where you must dynamically manage service endpoints. While Docker allows networking at the host level only (and Docker Swarm works across hosts), Kubernetes makes network management much easier containers in production. It includes commercially-supported distributions of Kubernetes, Mesos, and Docker Swarm for container orchestration, and allows teams to transparently view and manage the infrastructure

Respondents: 78 Docker Rocket Docker Swarm DockerHub Docker Trusted Registry Kubernetes Mesos 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Answer Choices Responses Docker Rocket Docker Swarm DockerHub DockerHub Docker Trusted Registry Kubernetes Mesos 24 / 37 2015 Jenkins Community Survey 30.11% 28 17.20% 16 41.94% 39 45.16% 42 Q24 If you are using Docker, what use- cases are you solving with it

Senior Software Engineer, ZTE li.guangxu@zte.com.cn Container and VM Ecosystem Kubernetes Docker Swarm Marathon Nomad Container OpenStack Others Why We Run VM on Kubernetes? • Traditional Applications k8s + docker + kata not easy kubernetes(dockershim) does not support to choose OCI runtime k8s + docker + kata not easy kata container network hotplug (support now) Dockershim / Docker Containerd pause container and app container b.create net resources in netns kubernetes k8s + docker + kata create pod k8s + docker + runc create pod How ZTE Uses kata container in NFV ZTE OpenPalette kubernetes

Node-Operator • Advanced Topic: Kube-on-Kube-Operator • Achievement • Q&A Background: DC/OS From Sigma 2.0(Swarm) to Sigma 3.1(Kubernetes) Background: Cluster Scale • Production environment: • Dozens of Cluster Order • Upgrade Nodes Versions • Upgrade Node 10.10.10.1 • Upgrade docker • Upgrade kubelet • Upgrade Node 10.10.10.2 • Upgrade docker • Upgrade kubelet …. Motivation: Work Order Deployment Disadvantages

still slow to go through the ship’s processors, But the electrician bee had a great idea. And so the swarm replaced legacy receivers, They installed and rewired a boosted antenna. eBPF enhances networking

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 7.31.1. Layering Docker Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . list each location as a separate import Configuration trees can also be used for Docker secrets. When a Docker swarm service is granted access to a secret, the secret gets mounted into the container possible to package a Spring Boot fat jar as a docker image. However, there are various downsides to copying and running the fat jar as is in the docker image. There’s always a certain amount of overhead

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 5.31.1. Layering Docker Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . list each location as a separate import Configuration trees can also be used for Docker secrets. When a Docker swarm service is granted access to a secret, the secret gets mounted into the container possible to package a Spring Boot fat jar as a docker image. However, there are various downsides to copying and running the fat jar as is in the docker image. There’s always a certain amount of overhead

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 7.31.1. Layering Docker Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . list each location as a separate import Configuration trees can also be used for Docker secrets. When a Docker swarm service is granted access to a secret, the secret gets mounted into the container possible to package a Spring Boot fat jar as a docker image. However, there are various downsides to copying and running the fat jar as is in the docker image. There’s always a certain amount of overhead

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 7.31.1. Layering Docker Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . list each location as a separate import Configuration trees can also be used for Docker secrets. When a Docker swarm service is granted access to a secret, the secret gets mounted into the container possible to package a Spring Boot fat jar as a docker image. However, there are various downsides to copying and running the fat jar as is in the docker image. There’s always a certain amount of overhead