<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Moby Project on Medium]]></title>
        <description><![CDATA[Stories by Moby Project on Medium]]></description>
        <link>https://medium.com/@Moby_Project?source=rss-b9159093ce3b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*StZmmUkDvAfpYIb7BDR4kw.jpeg</url>
            <title>Stories by Moby Project on Medium</title>
            <link>https://medium.com/@Moby_Project?source=rss-b9159093ce3b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:29:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Moby_Project/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[DockerCon EU Moby Summit: containerd]]></title>
            <link>https://medium.com/moby-blog/dockercon-eu-moby-summit-containerd-bbc72acec833?source=rss-b9159093ce3b------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbc72acec833</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[containerd]]></category>
            <category><![CDATA[dockercon]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Moby Project]]></dc:creator>
            <pubDate>Mon, 13 Nov 2017 16:57:16 GMT</pubDate>
            <atom:updated>2017-11-28T23:26:37.972Z</atom:updated>
            <content:encoded><![CDATA[<p>Following the<a href="https://blog.mobyproject.org/dockercon-eu-moby-summit-recap-moby-project-security-and-networking-16da4f8172f0"> first part</a> of this blog series on the DockerCon EU Moby Summit last month, we’re excited to share with you the slides and videos from the containerd talks.</p><p>In this first video below, containerd maintainers <a href="https://medium.com/u/b2d78b8b041a">Phil Estes</a> (IBM) and <a href="https://medium.com/u/d21a17509c63">Stephen Day</a> (Docker) share the latest updates on containerd as the project gets closer and closer to 1.0. In fact, containerd 1.0.0-beta.3 was just released yesterday! Test and pull requests welcome as always.</p><h3>containerd on Twitter</h3><p>containerd 1.0.0-beta.3! https://t.co/Cm3ctcCKGq</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpxqMUiQTVdw&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpxqMUiQTVdw%3Ffeature%3Doembed&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/efe9bc87204190f0f1de9cfee2a338f9/href">https://medium.com/media/efe9bc87204190f0f1de9cfee2a338f9/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FJd0j9T5BTcp9BL&amp;url=https%3A%2F%2Fwww.slideshare.net%2Fmobyproject%2Fthe-state-of-containerd-81537111&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fcontainerdupdate-mobysummit-2017dockerconeu1-171103013310-thumbnail-4.jpg%3Fcb%3D1509672827&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/3e1b0a9881681979b9feaccae2ef33fc/href">https://medium.com/media/3e1b0a9881681979b9feaccae2ef33fc/href</a></iframe><p>In this second video, <a href="https://medium.com/u/734fbd4421f">Lantao Liu</a> (Google) and <a href="https://medium.com/u/86f15227a034">Abhinandan prativadi</a> (Docker) share insights into the work they have done to integrate Kubernetes and containerd. You can find more information about this on the <a href="http://blog.kubernetes.io/2017/11/containerd-container-runtime-options-kubernetes.html">Kubernetes blo</a>g as well.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fqtzu84Qd25U%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dqtzu84Qd25U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fqtzu84Qd25U%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f2c78c371da77d4c57d81f3bdfc20199/href">https://medium.com/media/f2c78c371da77d4c57d81f3bdfc20199/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2F3uMi6AmxIzpCfu&amp;url=https%3A%2F%2Fwww.slideshare.net%2Fmobyproject%2Fcricontainerd&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fcri-containerd-171107000048-thumbnail-4.jpg%3Fcb%3D1510012881&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/5c38124544043345b7f18bfd4aa6e13c/href">https://medium.com/media/5c38124544043345b7f18bfd4aa6e13c/href</a></iframe><h3>Nigel Poulton on Twitter</h3><p>Get in! Loads more #Kubernetes stuff today at #MobySummit</p><p>In case you want to learn more about containerd and what’s under the hood of the project, I recommend you watch the talk below by S<a href="https://twitter.com/scottcoulton">cott Coulton</a> (Puppet) or read the latest blog post on <a href="https://blog.mobyproject.org/containerd-namespaces-for-docker-kubernetes-and-beyond-d6c43f565084">containerd namespaces for Docker, Kubernetes, and beyond</a> by <a href="https://medium.com/u/dbb74531adf5">Michael Crosby</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FfIRaPGxhsH0%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DfIRaPGxhsH0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FfIRaPGxhsH0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3dfb260f1fe19467f4f414921440b25c/href">https://medium.com/media/3dfb260f1fe19467f4f414921440b25c/href</a></iframe><p>Learn more about containerd:</p><ul><li><a href="https://blog.mobyproject.org/getting-started-with-containerd-a81fa090982f">Get started with containerd</a></li><li><a href="https://blog.mobyproject.org/kubernetes-cluster-with-containerd-and-cri-containerd-eb77c989c885">Get started with CRI-containerd</a></li><li>Check out the <a href="https://github.com/containerd/containerd">containerd repo</a></li><li>Join the <a href="http://dockr.ly/community">#containerd channel</a> on slack</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbc72acec833" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moby-blog/dockercon-eu-moby-summit-containerd-bbc72acec833">DockerCon EU Moby Summit: containerd</a> was originally published in <a href="https://medium.com/moby-blog">Moby Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Cluster with Containerd and CRI-Containerd]]></title>
            <link>https://medium.com/moby-blog/kubernetes-cluster-with-containerd-and-cri-containerd-eb77c989c885?source=rss-b9159093ce3b------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb77c989c885</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[cri-containerd]]></category>
            <category><![CDATA[containerd]]></category>
            <dc:creator><![CDATA[Moby Project]]></dc:creator>
            <pubDate>Wed, 27 Sep 2017 23:11:39 GMT</pubDate>
            <atom:updated>2017-09-27T23:11:39.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/196/1*8Tdv1PJWXUfk8Pa8bcHq-Q.png" /></figure><p>This document provides the steps to bring up a Kubernetes cluster using ansible and kubeadm tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*67YUWQuhWdiNg_3vPMSHTA.png" /></figure><ul><li>OS: Ubuntu 16.04 (will be updated with additional distros after testing)</li><li>Python: 2.7+</li><li>Ansible: 2.3+</li></ul><h3>Step 0:</h3><ul><li>Install Ansible on the host where you will provision the cluster. This host may be one of the nodes you plan to include in your cluster. Installation instructions for Ansible are found <a href="http://docs.ansible.com/ansible/latest/intro_installation.html">here</a>.</li><li>Create a hosts file and include the IP addresses of the hosts that need to be provisioned by Ansible.</li></ul><pre>$ cat hosts<br>172.31.7.230<br>172.31.13.159<br>172.31.1.227</pre><ul><li>Setup passwordless SSH access from the host where you are running Ansible to all the hosts in the hosts file. The instructions can be found in <a href="http://www.linuxproblem.org/art_9.html">here</a></li></ul><h3>Step 1:</h3><p>At this point, the ansible playbook should be able to ssh into the machines in the hosts file.</p><pre>git clone <a href="https://github.com/kubernetes-incubator/cri-containerd">https://github.com/kubernetes-incubator/cri-containerd</a><br>cd ./cri-containerd/contib/ansible<br>ansible-playbook -i hosts cri-containerd.yaml</pre><p>A typical cloud login might have a username and private key file, in which case the following can be used:</p><pre>ansible-playbook -i hosts -u &lt;username&gt; --private-key &lt;example.pem&gt; cri-containerd.yaml</pre><p>For more options ansible config file (/etc/ansible/ansible.cfg) can be used to set defaults. Please refer to <a href="http://docs.ansible.com/ansible/latest/intro_configuration.html">Ansible options</a> for advanced ansible configurations.</p><p>At the end of this step, you will have the required software installed in the hosts to bringup a kubernetes cluster.</p><pre>PLAY RECAP ***************************************************************************************************************************************************************<br>172.31.1.227               : ok=21   changed=7    unreachable=0    failed=0<br>172.31.13.159              : ok=21   changed=7    unreachable=0    failed=0<br>172.31.7.230               : ok=21   changed=7    unreachable=0    failed=0</pre><h3>Step 2:</h3><p>Use <a href="https://kubernetes.io/docs/setup/independent/install-kubeadm/">kubeadm</a> to bring up a Kubernetes Cluster. Depending on what third-party provider you choose, you might have to set the --pod-network-cidr to something provider-specific. Initialize the cluster from one of the nodes (Note: This node will be the master node):</p><pre>$sudo kubeadm init --skip-preflight-checks<br>[kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.<br>[init] Using Kubernetes version: v1.7.6<br>[init] Using Authorization modes: [Node RBAC]<br>[preflight] Skipping pre-flight checks<br>[kubeadm] WARNING: starting in 1.8, tokens expire after 24 hours by default (if you require a non-expiring token use --token-ttl 0)<br>[certificates] Generated CA certificate and key.<br>[certificates] Generated API server certificate and key.<br>[certificates] API Server serving cert is signed for DNS names [abhi-k8-ubuntu-1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.31.7.230]<br>[certificates] Generated API server kubelet client certificate and key.<br>[certificates] Generated service account token signing key and public key.<br>[certificates] Generated front-proxy CA certificate and key.<br>[certificates] Generated front-proxy client certificate and key.<br>[certificates] Valid certificates and keys now exist in &quot;/etc/kubernetes/pki&quot;<br>[kubeconfig] Wrote KubeConfig file to disk: &quot;/etc/kubernetes/admin.conf&quot;<br>[kubeconfig] Wrote KubeConfig file to disk: &quot;/etc/kubernetes/kubelet.conf&quot;<br>[kubeconfig] Wrote KubeConfig file to disk: &quot;/etc/kubernetes/controller-manager.conf&quot;<br>[kubeconfig] Wrote KubeConfig file to disk: &quot;/etc/kubernetes/scheduler.conf&quot;<br>[apiclient] Created API client, waiting for the control plane to become ready<br>[apiclient] All control plane components are healthy after 42.002391 seconds<br>[token] Using token: 43a25d.420ff2e06336e4c1<br>[apiconfig] Created RBAC rules<br>[addons] Applied essential addon: kube-proxy<br>[addons] Applied essential addon: kube-dns</pre><pre>Your Kubernetes master has initialized successfully!</pre><pre>To start using your cluster, you need to run (as a regular user):</pre><pre>  mkdir -p $HOME/.kube<br>  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config<br>  sudo chown $(id -u):$(id -g) $HOME/.kube/config</pre><pre>You should now deploy a pod network to the cluster.<br>Run &quot;kubectl apply -f [podnetwork].yaml&quot; with one of the options listed at:<br>  <a href="http://kubernetes.io/docs/admin/addons/">http://kubernetes.io/docs/admin/addons/</a></pre><pre>You can now join any number of machines by running the following on each node<br>as root:</pre><pre>  kubeadm join --token 43a25d.420ff2e06336e4c1 172.31.7.230:6443</pre><h3>Step 3:</h3><p>Use kubeadm join to add each of the remaining nodes to your cluster. (Note: Uses token that was generated during cluster init.)</p><pre>$sudo kubeadm join --token 43a25d.420ff2e06336e4c1 172.31.7.230:6443 --skip-preflight-checks<br>[kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.<br>[preflight] Skipping pre-flight checks<br>[discovery] Trying to connect to API Server &quot;172.31.7.230:6443&quot;<br>[discovery] Created cluster-info discovery client, requesting info from &quot;https://172.31.7.230:6443&quot;<br>[discovery] Cluster info signature and contents are valid, will use API Server &quot;https://172.31.7.230:6443&quot;<br>[discovery] Successfully established connection with API Server &quot;172.31.7.230:6443&quot;<br>[bootstrap] Detected server version: v1.7.6<br>[bootstrap] The server supports the Certificates API (certificates.k8s.io/v1beta1)<br>[csr] Created API client to obtain unique certificate for this node, generating keys and certificate signing request<br>[csr] Received signed certificate from the API server, generating KubeConfig...<br>[kubeconfig] Wrote KubeConfig file to disk: &quot;/etc/kubernetes/kubelet.conf&quot;</pre><pre>Node join complete:<br>* Certificate signing request sent to master and response<br>  received.<br>* Kubelet informed of new secure connection details.</pre><pre>Run &#39;kubectl get nodes&#39; on the master to see this machine join.</pre><p>At the end of Step 3 you should have a kubernetes cluster up and running and ready for deployment.</p><h3>Step 4:</h3><p>Please follow the instructions <a href="https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#pod-network">here</a> to deploy CNI network plugins and start a demo app.</p><p>We are constantly striving to improve the installer. Please feel free to open issues and provide suggestions to make the installer fast and easy to use. We are open to receiving help in validating and improving the installer on different distros.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb77c989c885" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moby-blog/kubernetes-cluster-with-containerd-and-cri-containerd-eb77c989c885">Kubernetes Cluster with Containerd and CRI-Containerd</a> was originally published in <a href="https://medium.com/moby-blog">Moby Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes and LinuxKit]]></title>
            <link>https://medium.com/moby-blog/kubernetes-and-linuxkit-db6525f862b?source=rss-b9159093ce3b------2</link>
            <guid isPermaLink="false">https://medium.com/p/db6525f862b</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[linuxkit]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[moby-project]]></category>
            <dc:creator><![CDATA[Moby Project]]></dc:creator>
            <pubDate>Wed, 27 Sep 2017 22:45:06 GMT</pubDate>
            <atom:updated>2017-09-27T22:45:06.026Z</atom:updated>
            <content:encoded><![CDATA[<p>This project aims to demonstrate how one can create minimal and immutable Kubernetes OS images with LinuxKit.</p><p>Make sure to cd projects/kubernetes first.</p><p>Build OS images:</p><pre>make build-vm-images</pre><p>By default this will build images using Docker Engine for execution. To instead use cri-containerd use:</p><pre>make build-vm-images KUBE_RUNTIME=cri-containerd</pre><p>Boot Kubernetes master OS image using hyperkit on macOS: or qemu on Linux:</p><pre>./boot.sh</pre><p>Get IP address of the master:</p><pre>ip addr show dev eth0</pre><p>Login to the kubelet container:</p><pre>./ssh_into_kubelet.sh &lt;master-ip&gt;</pre><p>Manually initialise master with kubeadm:</p><pre>kubeadm-init.sh</pre><p>Once kubeadm exits, make sure to copy the kubeadm join arguments, and try kubectl get nodes from within the master.</p><p>If you just want to run a single node cluster with jobs running on the master, you can use:</p><pre>kubectl taint nodes --all node-role.kubernetes.io/master- --kubeconfig /etc/kubernetes/admin.conf</pre><p>To boot a node use:</p><pre>./boot.sh &lt;n&gt; [&lt;join_args&gt; ...]</pre><p>More specifically, to start 3 nodes use 3 separate shells and run this:</p><pre>shell1&gt; ./boot.sh 1 --token bb38c6.117e66eabbbce07d 192.168.65.22:6443<br>shell2&gt; ./boot.sh 2 --token bb38c6.117e66eabbbce07d 192.168.65.22:6443<br>shell3&gt; ./boot.sh 3 --token bb38c6.117e66eabbbce07d 192.168.65.22:6443</pre><h3>Platform specific information</h3><h3>MacOS</h3><p>The above instructions should work as is.</p><h3>Linux</h3><p>By default linuxkit run uses user mode networking which does not support access from the host. To workaround this you can use port forwarding e.g.</p><pre>KUBE_RUN_ARGS=&quot;-publish 2222:22&quot; ./boot.sh</pre><pre>ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -p 2222 root@localhost</pre><p>However you will not be able to run worker nodes since individual instances cannot see each other.</p><p>To enable networking between instance unfortunately requires root privileges to configure a bridge and setup the bridge mode privileged helper.</p><p>See <a href="http://wiki.qemu.org/Features/HelperNetworking">http://wiki.qemu.org/Features/HelperNetworking</a> for details in brief you will need:</p><ul><li>To setup and configure a bridge (including e.g. DHCP etc) on the host. (You can reuse a bridge created by e.g. virt-mananger)</li><li>To set the qemu-bridge-helper setuid root. The location differs by distro, it could be /usr/lib/qemu/qemu-bridge-helper or /usr/local/libexec/qemu-bridge-helper or elsewhere. You need to chmod u+s «PATH».</li><li>List the bridge created in the first step in /etc/qemu/bridge.conf with a line like allow br0 (if your bridge is called br0).</li><li>Set KUBE_NETWORKING=bridge,«name» e.g.</li><li>KUBE_NETWORKING=”bridge,br0&quot; ./boot.sh KUBE_NETWORKING=”bridge,br0&quot; ./boot.sh 1 «options»</li></ul><h3>Configuration</h3><p>The boot.sh script has various configuration variables at the top which can be overridden via the environment e.g.</p><pre>KUBE_VCPUS=4 ./boot.sh</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db6525f862b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moby-blog/kubernetes-and-linuxkit-db6525f862b">Kubernetes and LinuxKit</a> was originally published in <a href="https://medium.com/moby-blog">Moby Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moby Summit Los Angeles recap]]></title>
            <link>https://medium.com/moby-blog/moby-summit-los-angeles-recap-a41e6acf81f8?source=rss-b9159093ce3b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a41e6acf81f8</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[moby-project]]></category>
            <category><![CDATA[linuxkit]]></category>
            <dc:creator><![CDATA[Moby Project]]></dc:creator>
            <pubDate>Mon, 25 Sep 2017 18:17:03 GMT</pubDate>
            <atom:updated>2017-09-25T18:54:07.142Z</atom:updated>
            <content:encoded><![CDATA[<p>Two weeks ago, member of the Docker team and Open Source community were in Los Angeles for a Moby Project Summit alongside Open Source Summit North America (previously known as LinuxCon). This was the 3rd Moby Summit edition since <a href="https://medium.com/u/a74e37a3408d">Solomon Hykes</a> introduced the <a href="https://blog.docker.com/2017/04/introducing-the-moby-project/">Moby Project: a new open-source project to advance the software containerization movement</a> at DockerCon 2017 in Austin.</p><p>This summit is for container users who are actively maintaining, contributing or generally involved in the design and development of the Moby Project and it’s components: runC, containerd, LinuxKit, Infrakit, SwarmKit, HyperKit, DataKit, VPNKit, Notary, libnetwork, etc.</p><p>We followed the same format as previous summits with talks in the morning and birds of a feather (BOF) sessions in the afternoon. Unfortunately the talks were not recorded but you can find the slides below:</p><h3>containerd Internals by <a href="https://medium.com/u/d21a17509c63">Stephen Day</a></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FjFeg71hlzakVRA&amp;url=https%3A%2F%2Fwww.slideshare.net%2FDocker%2Fassessing-container-runtime-performance-with-bucketbench-by-phil-estes-ibm&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fcontainerd-ossla-170920080509-thumbnail-4.jpg%3Fcb%3D1505894752&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/e9497d2c3028633eac03d5df5a5ea7ad/href">https://medium.com/media/e9497d2c3028633eac03d5df5a5ea7ad/href</a></iframe><h3>Kubernetes containerd integration by <a href="https://medium.com/u/30104106fe60">Liu Lantao</a></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FK41Ft9AiQEYtCA&amp;url=https%3A%2F%2Fwww.slideshare.net%2FDocker%2Fkubernetes-cri-containerd-integration-by-lantao-liu-google&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fcri-containerd-170920075844-thumbnail-4.jpg%3Fcb%3D1505894665&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/482f82b3f4f1cece911f7e45403ec7c6/href">https://medium.com/media/482f82b3f4f1cece911f7e45403ec7c6/href</a></iframe><h3>Assessing container runtime performance with bucketbench by <a href="https://twitter.com/estesp">Phil Estes</a></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FtVy9lpDl2ELcQO&amp;url=https%3A%2F%2Fwww.slideshare.net%2FPhilEstes%2Fbucketbench-benchmarking-container-runtime-performance&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fmobysummitl-170918195709-thumbnail-4.jpg%3Fcb%3D1505765009&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/772b33cad52a92d810267f0dc2fd64a8/href">https://medium.com/media/772b33cad52a92d810267f0dc2fd64a8/href</a></iframe><h3>LinuxKit the first 5 months by <a href="https://twitter.com/justincormack">@justincormack</a> and @riyazfaizullabhoy</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2F7rjG8MkDSjHJf0&amp;url=https%3A%2F%2Fwww.slideshare.net%2FDocker%2Flinuxkit-the-first-five-months-by-justin-cormack-riyaz-faizullabhoy-docker&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Flinuxkitmobysummitla-170920080020-thumbnail-4.jpg%3Fcb%3D1505894680&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/9d963b9cc361bacc4a9be32f2b4f47d6/href">https://medium.com/media/9d963b9cc361bacc4a9be32f2b4f47d6/href</a></iframe><h3>Buildkit by <a href="https://twitter.com/tonistiigi">Tonis Tiigi</a></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FCYHUMqrCPFtoYm&amp;url=https%3A%2F%2Fwww.slideshare.net%2FDocker%2Fstate-of-builder-and-buildkit&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fbuildkitossna-170920080230-thumbnail-4.jpg%3Fcb%3D1505894644&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/eb7cc3f137401f6631ea077dc86544b5/href">https://medium.com/media/eb7cc3f137401f6631ea077dc86544b5/href</a></iframe><h3>Security Scanning &amp; Notary &amp; <a href="https://twitter.com/CloudNativeFdn">CNCF</a> donation by <a href="https://medium.com/u/11ab0f4d3586">David Lawrence</a></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2F3YMG5TE7y10bCh&amp;url=https%3A%2F%2Fwww.slideshare.net%2FDocker%2Fsecurity-scanning-notary-cncf-donation-by-david-lawrence-docker&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fsigningscanningmobysummitla2017-170920080137-thumbnail-4.jpg%3Fcb%3D1505894615&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/96689d143dcfbf49ccd3b35d3f31dc97/href">https://medium.com/media/96689d143dcfbf49ccd3b35d3f31dc97/href</a></iframe><p>The LA Moby Summit showed the impressive progress on all fronts for Moby projects. We had talks, demos and BOFs about containerd getting ready for 1.0, containerd integration in Kubernetes via <a href="https://github.com/kubernetes-incubator/cri-containerd">cri-containerd</a>, libnetwork drivers used as CNI plugins, bucketbench to test the performance of container runtimes, LinuxKit progress towards Arm64, support for Linux Containers On Windows, Wireguard and Kubernetes, the incubation of many security projects in LinuxKit security SIG, the <a href="https://github.com/cncf/toc/pull/38">in-progress contribution of Notary and TUF to CNCF</a>, progress of the Security scanning Moby SIG, and introduction of BuildKit, a toolkit for building software based on OCI specifications and containerd. All these advances together start to paint a picture of the innovations that the componentization of the Docker codebase in the Moby project enables.</p><h3>chanezon on Twitter</h3><p>MobySummit @APrativadi doing the first public demo of cri-containerd, @kubernetesio + @containerd + libnetwork drivers used as CNI plugins</p><p>A big thank you to the <a href="https://www.cncf.io/">Cloud Native Computing Foundation (CNCF)</a> for sponsoring the containerd sessions and BOF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/271/0*sqfVYFD8qOPxYxyX." /></figure><p>Next <a href="https://europe-2017.dockercon.com/agenda/">Moby Summit at DockerCon EU in Copenhagen</a> should be exciting. We hope to see many of you there!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a41e6acf81f8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moby-blog/moby-summit-los-angeles-recap-a41e6acf81f8">Moby Summit Los Angeles recap</a> was originally published in <a href="https://medium.com/moby-blog">Moby Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moby Summit at OSS North America]]></title>
            <link>https://medium.com/moby-blog/moby-summit-alongside-open-source-summit-north-america-405d5f57b723?source=rss-b9159093ce3b------2</link>
            <guid isPermaLink="false">https://medium.com/p/405d5f57b723</guid>
            <category><![CDATA[moby-project]]></category>
            <category><![CDATA[linuxkit]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[containerd]]></category>
            <dc:creator><![CDATA[Moby Project]]></dc:creator>
            <pubDate>Wed, 23 Aug 2017 16:30:17 GMT</pubDate>
            <atom:updated>2017-08-24T05:37:32.585Z</atom:updated>
            <content:encoded><![CDATA[<p>In case you missed it, the next <a href="https://www.eventbrite.com/e/moby-summit-los-angeles-tickets-35930560273">Moby Project Summi</a>t will take place on <strong>September 14, 2017 in Los Angeles</strong>, as part of the Open Source Summit North America. Following the success of the previous editions, we’ll keep the same format which consists of short technical talks / demos in the morning and Birds-of-a-Feather sessions in the afternoon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fHc2PtgPzkYDoBGl." /></figure><p>We have an excellent line up of speakers in store for you and are excited to share the agenda below. We hope that these sessions inspire you to come participate in the Moby community and <a href="https://www.eventbrite.com/e/moby-summit-los-angeles-tickets-35930560273">register for this Moby summit</a>.</p><h3>AGENDA</h3><p><strong>8:00am — 9:00am — Registration &amp; Breakfast</strong></p><p>9am — 9:30am: Introduction to the Moby Project &amp; collaboration with CNCF (Patrick Chanezon &amp; Manik Taneja)</p><p><strong>9:30am — 10:30am — containerd talks</strong></p><ul><li>Latest update on containerd by <a href="https://medium.com/u/d21a17509c63">Stephen Day</a> (Docker)</li></ul><p>In this talk, Stephen will cover the progress of containerd, the adjusted scope and open items the team has been working on with the help of the community. Attendees will also be provided information on what containerd means for them and how it has shaped new upstream container initiatives.</p><ul><li>Kubernetes CRI containerd integration by Lantao Lio (Google)</li></ul><p>The talk will firstly give a brief review of the runtime portability of Kubernetes, then talk about why containerd is attractive to Kubernetes, and then give a brief introduction and status update of Kubernetes Containerd Integration and a demo.</p><ul><li>Assessing container runtime performance with bucketbench by Phil Estes (IBM)</li></ul><p>In this talk, we’ll briefly overview of the OpenWhisk serverless (function-as-a-service) framework that initially used the full Docker container engine as the execution vehicle for invoking user functions via containers. After several performance and stability challenges, this project decided to assess the various layers of the Docker engine (containerd and runC) as potential options for the function invoker. Out of that work came an open source project, bucketbench, that can be used to generate benchmarks of container lifecycle operations (e.g., start, stop, kill, remove, pause, unpause) and compare multithreaded operation throughput and stability of each optional engine.</p><p>This talk will provide details on the bucketbench project, explain how it has been used to generate performance data for these container runtimes, and shares lessons learned along the way that greatly impact container runtime performance, including bottlenecks in the Linux kernel.</p><p>In this talk you’ll learn how you can use bucketbench for your own performance tuning or assessment of container runtimes and how you can collaborate on improvements to the bucketbench project.</p><p><strong>10:30am — 12:00pm — LinuxKit &amp; Security talks</strong></p><ul><li>LinuxKit: the first five months by Justin Cormack &amp; Riyaz Faizullabhoy (Docker)</li></ul><p>LinuxKit was launched five months ago, and has received a huge number of contributions from the Moby community. This talk will cover some of the large number of areas the community has contributed to, including: ARM64 support, bare metal support, containerd-cri integration with system containers and Kubernetes running on the same containerd and Wireguard for encrypted networking.</p><ul><li>Security Scanning &amp; Notary &amp; CNCF donation by David Lawrence (Docker)</li></ul><p>Get updates on the Notary &amp; TUF donation to CNCF along with information on proposed additions to the TUF specification. TUF is a living specification and there are a number of interesting proposals that have been submitted to meet distributed trust use cases, allowing one to incorporate multiple sources of trust into a process.</p><p>We’ll also look at what SIG Scanning has been up to and what the group will be taking on in the future. Find out about some of the standards we’re looking at integrating and the main use cases we believe SIG Scanning can help address.</p><p><strong>12:00–1:00m — Lunch</strong></p><p><strong>1:00pm — 3:30pm — Birds of a Feather</strong></p><ol><li>runC / containerd</li><li>LinuxKit</li><li>Security</li></ol><p><strong>3:30pm — 4:00pm — BOFs recap + AMA / panel</strong></p><p>A big thank you to the <a href="https://www.cncf.io/">Cloud Native Computing Foundation (CNCF)</a> for sponsoring the containerd sessions and BOF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/271/0*k-NoYOT_nHOEUtw4." /></figure><p>We hope to see you there! <a href="https://www.eventbrite.com/e/moby-summit-los-angeles-tickets-35930560273">Register today</a> to save your spot.</p><h3>Moby on Twitter</h3><p>Check out the Agenda for the upcoming @moby Summit in LA on Sep 14th https://t.co/8YSRYxrCWw cc @estesp @stevvooe @chanezon #OSSummit</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=405d5f57b723" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moby-blog/moby-summit-alongside-open-source-summit-north-america-405d5f57b723">Moby Summit at OSS North America</a> was originally published in <a href="https://medium.com/moby-blog">Moby Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started with containerd]]></title>
            <link>https://medium.com/moby-blog/getting-started-with-containerd-a81fa090982f?source=rss-b9159093ce3b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a81fa090982f</guid>
            <category><![CDATA[containerd]]></category>
            <category><![CDATA[moby-project]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[golang]]></category>
            <dc:creator><![CDATA[Moby Project]]></dc:creator>
            <pubDate>Thu, 17 Aug 2017 20:00:56 GMT</pubDate>
            <atom:updated>2017-08-17T20:00:56.115Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many different ways to use containerd. If you are a developer working on containerd you can use the ctr tool to quickly test features and functionality without writing extra code. However, if you want to integrate containerd into your project we have an easy to use client package that allows you to work with containerd.</p><p>In this guide we will pull and run a redis server with containerd using the client package. We will assume that you are running a modern linux host for this example with a compatible build of runc .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/0*zUsvG0T8RssQvPl4." /></figure><h3>Starting containerd</h3><p>You can download one of the latest builds for containerd on the <a href="https://github.com/containerd/containerd/releases">github releases</a> page and then use your favorite process supervisor to get the daemon started. If you are using systemd, we have a containerd.service file at the root of the repository that you can use.</p><p>The daemon also uses a configuration file located in /etc/containerd/config.toml for specifying daemon level options. A sample configuration file looks like this:</p><pre>subreaper = true<br>oom_score = -999</pre><pre>[debug]<br> level = “debug”</pre><pre>[metrics]<br> address = “127.0.0.1:1338”</pre><pre>[plugins.linux]<br> runtime = “runc”<br> shim_debug = true</pre><p>The default configuration can be generated via containerd config default &gt; /etc/containerd/config.toml</p><h3>Connecting to containerd</h3><p>We will start a new main.go file and import the containerd root package that contains the client.</p><pre>package main</pre><pre>import (<br> “log”</pre><pre>“github.com/containerd/containerd”<br>)</pre><pre>func main() {<br> if err := redisExample(); err != nil {<br> log.Fatal(err)<br> }<br>}</pre><pre>func redisExample() error {<br> client, err := containerd.New(“/run/containerd/containerd.sock”)<br> if err != nil {<br> return err<br> }<br> defer client.Close()<br> return nil<br>}</pre><p>This will create a new client with the default containerd socket path. Because we are working with a daemon over GRPC we need to create a context for use with calls to client methods. containerd is also namespaced for callers of the API. We should also set a namespace for our guide after creating the context.</p><p>ctx := namespaces.WithNamespace(context.Background(), “example”)</p><p>Having a namespace for our usage ensures that containers, images, and other resources without containerd do not conflict with other users of a single daemon.</p><h3>Pulling the redis image</h3><p>Now that we have a client to work with we need to pull an image. We can use the redis image based on alpine linux from the DockerHub.</p><pre>image, err := client.Pull(ctx, “docker.io/library/redis:alpine”, containerd.WithPullUnpack)<br> if err != nil {<br> return err<br> }</pre><p>The containerd client uses the Opts pattern for many of the method calls. We use the containerd.WithPullUnpackso that we not only fetch and download the content into containerd’s content store but also unpack it into a snapshotter for use as a root filesystem.</p><h3>Creating an OCI Spec and Container</h3><p>Now that we have an image to base our container off of, we need to generate an OCI runtime specification that the container can be based off of.</p><p>containerd provides reasonable defaults for generating OCI runtime specs. There is also an Opt for modifying the default config based on the image that we pulled.</p><pre>spec, err := containerd.GenerateSpec(containerd.WithImageConfig(ctx, image))<br> if err != nil {<br> return err<br> }</pre><p>After we have a spec generated we need to create a container. The container will be based off of the image, use the runtime information in the spec that was just created, and we will allocate a new read-write snapshot so the container can store any persistent information.</p><pre>container, err := client.NewContainer(<br> ctx,<br> “redis-server”,<br> containerd.WithSpec(spec),<br> containerd.WithImage(image),<br> containerd.WithNewSnapshot(“redis-server-snapshot”, image),<br> )<br> if err != nil {<br> return err<br> }<br> defer container.Delete(ctx, containerd.WithSnapshotCleanup)</pre><p>When creating a new snapshot for the container we need to provide a snapshot ID as well as the Image that the container will be based on. By providing a separate snapshot ID than the container ID we can easily reuse, existing snapshots across different containers.</p><p>We also add a line to delete the container along with its snapshot after we are done with this example.</p><h3>Creating a running Task</h3><p>One thing that may be confusing at first for new containerd users is the separation between a Container and a Task. A container is a metadata object that resources are allocated and attached to. A task is a live, running process on the system. Tasks should be deleted after each run while a container can be used, updated, and queried multiple times.</p><pre>task, err := container.NewTask(ctx, containerd.Stdio)<br> if err != nil {<br> return err<br> }<br> defer task.Delete(ctx)</pre><p>The new task that we just created is actually a running process on your system. We use the containerd.Stdio Optso that all IO from the container is sent to our main.go process.</p><p>If you are familiar with the OCI runtime actions, the task is currently in the “created” state. This means that the namespaces, root filesystem, and various container level settings have been initialized but the user defined process, in this example “redis-server”, has not been started. This gives users a chance to setup network interfaces or attach different tools to monitor the container. containerd also takes this opportunity to monitor your container as well. Waiting on things like the container’s exit status and cgroup metrics are setup at this point.</p><p>If you are familiar with prometheus you can curl the containerd metrics endpoint (in the config.toml that we created) to see your container’s metrics:</p><pre>&gt; curl 127.0.0.1:1228/metrics</pre><p>Pretty cool right?</p><h3>Task Wait and Start</h3><p>Now that we have a task in the created state we need to make sure we that we wait on the task to exit so that we can close our example and cleanup the resources that we created. You always want to make sure you Wait before calling Start on a task. This makes sure that you do not encounter any races if the task has a simple program like /bin/true that exits promptly after calling start.</p><pre>exitStatusC := make(chan uint32, 1)<br> go func() {<br> status, err := task.Wait(ctx)<br> if err != nil {<br> fmt.Println(err)<br> }<br> exitStatusC &lt;- status<br> }()</pre><pre>if err := task.Start(ctx); err != nil {<br> return err<br> }</pre><p>Now we should see the redis-server logs in our terminal when we run the main.go file.</p><h3>Killing the task</h3><p>Since we are running a long running server we will need to kill the task in order to exit out of our example. To do this we will simply call Kill on the task after waiting a couple of seconds so we have a chance to see the redis-server logs.</p><pre>time.Sleep(3 * time.Second)</pre><pre>if err := task.Kill(ctx, syscall.SIGTERM); err != nil {<br> return err<br> }</pre><pre>status := &lt;-exitStatusC<br> fmt.Printf(“redis-server exited with status: %d\n”, status)</pre><p>We wait on our exit status channel that we setup to ensure the task has fully exited and we get the exit status. If you have to reload containers or miss waiting on a task, Delete will also return the exit status when you finally delete the task. We got you covered</p><pre>status, err := task.Delete(ctx)</pre><h3>Full Example</h3><p>Here is the full example that we just put together.</p><pre>package main</pre><pre>import (<br> “context”<br> “fmt”<br> “log”<br> “syscall”<br> “time”</pre><pre>“github.com/containerd/containerd”<br> “github.com/containerd/containerd/namespaces”<br>)</pre><pre>func main() {<br> if err := redisExample(); err != nil {<br> log.Fatal(err)<br> }<br>}</pre><pre>func redisExample() error {<br> // create a new client connected to the default socket path for containerd<br> client, err := containerd.New(“/run/containerd/containerd.sock”)<br> if err != nil {<br> return err<br> }<br> defer client.Close()</pre><pre>// create a new context with an “example” namespace<br> ctx := namespaces.WithNamespace(context.Background(), “example”)</pre><pre>// pull the redis image from DockerHub<br> image, err := client.Pull(ctx, “docker.io/library/redis:alpine”, containerd.WithPullUnpack)<br> if err != nil {<br> return err<br> }</pre><pre>// generate an OCI runtime spec using the Args, Env, etc from the redis image that we pulled<br> spec, err := containerd.GenerateSpec(containerd.WithImageConfig(ctx, image))<br> if err != nil {<br> return err<br> }</pre><pre>// create a container<br> container, err := client.NewContainer(<br> ctx,<br> “redis-server”,<br> containerd.WithSpec(spec),<br> containerd.WithImage(image),<br> containerd.WithNewSnapshot(“redis-server-snapshot”, image),<br> )<br> if err != nil {<br> return err<br> }<br> defer container.Delete(ctx, containerd.WithSnapshotCleanup)</pre><pre>// create a task from the container<br> task, err := container.NewTask(ctx, containerd.Stdio)<br> if err != nil {<br> return err<br> }<br> defer task.Delete(ctx)</pre><pre>// make sure we wait before calling start<br> exitStatusC := make(chan uint32, 1)<br> go func() {<br> status, err := task.Wait(ctx)<br> if err != nil {<br> fmt.Println(err)<br> }<br> exitStatusC &lt;- status<br> }()</pre><pre>// call start on the task to execute the redis server<br> if err := task.Start(ctx); err != nil {<br> return err<br> }</pre><pre>// sleep for a lil bit to see the logs<br> time.Sleep(3 * time.Second)</pre><pre>// kill the process and get the exit status<br> if err := task.Kill(ctx, syscall.SIGTERM); err != nil {<br> return err<br> }</pre><pre>// wait for the process to fully exit and print out the exit status</pre><pre>status := &lt;-exitStatusC<br> fmt.Printf(“redis-server exited with status: %d\n”, status)</pre><pre>return nil<br>}</pre><p>We can build this example and run it as follows to see our hard work come together.</p><pre>&gt; go build -o example main.go<br>&gt; sudo ./example</pre><pre>1:C 04 Aug 20:41:37.682 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo<br>1:C 04 Aug 20:41:37.682 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started<br>1:C 04 Aug 20:41:37.682 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf<br>1:M 04 Aug 20:41:37.682 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.<br>1:M 04 Aug 20:41:37.682 # Server can’t set maximum open files to 10032 because of OS error: Operation not permitted.<br>1:M 04 Aug 20:41:37.682 # Current maximum open files is 1024. maxclients has been reduced to 992 to compensate for low ulimit. If you need higher maxclients increase ‘ulimit -n’.<br>1:M 04 Aug 20:41:37.683 * Running mode=standalone, port=6379.<br>1:M 04 Aug 20:41:37.683 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.<br>1:M 04 Aug 20:41:37.684 # Server initialized<br>1:M 04 Aug 20:41:37.684 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.<br>1:M 04 Aug 20:41:37.684 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never &gt; /sys/kernel/mm/transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.<br>1:M 04 Aug 20:41:37.684 * Ready to accept connections<br>1:signal-handler (1501879300) Received SIGTERM scheduling shutdown…<br>1:M 04 Aug 20:41:40.791 # User requested shutdown…<br>1:M 04 Aug 20:41:40.791 * Saving the final RDB snapshot before exiting.<br>1:M 04 Aug 20:41:40.794 * DB saved on disk<br>1:M 04 Aug 20:41:40.794 # Redis is now ready to exit, bye bye…<br>redis-server exited with status: 0</pre><p>In the end, we really did not write that much code when you use the client package.</p><p>I hope this guide helped to get you up and running with containerd. Feel free to join the <a href="https://dockr.ly/community">slack channel</a> if you have any questions and like all things, if you want to help contribute to containerd or this guide, submit a pull request.</p><h3>Michael Crosby on Twitter</h3><p>If you want to try out @containerd we added a quick Getting Started Guide: https://t.co/QxQHoTnNzS</p><p><strong>Learn More about containerd</strong></p><ul><li>Read about <a href="https://blog.docker.com/2017/08/what-is-containerd-runtime/">what’s containerd</a> ?</li><li>Follow the guide on <a href="https://t.co/MAc2HOb8mn">configuration for ops/admins</a></li><li>Check out the videos &amp; slides from the past <a href="https://blog.docker.com/2017/02/containerd-summit-recap-slides-videos-meeting-notes/">containerd summit</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a81fa090982f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moby-blog/getting-started-with-containerd-a81fa090982f">Getting started with containerd</a> was originally published in <a href="https://medium.com/moby-blog">Moby Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>