<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containers on Sébastien Han</title><link>http://sebastien-han.fr/tags/containers/</link><description>Recent content in Containers on Sébastien Han</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 17 May 2019 22:59:04 +0000</lastBuildDate><atom:link href="http://sebastien-han.fr/tags/containers/atom.xml" rel="self" type="application/rss+xml"/><item><title>Rook just landed on operatorhub.io</title><link>http://sebastien-han.fr/blog/2019/05/17/Rook-just-landed-on-operatorhub-io/</link><pubDate>Fri, 17 May 2019 22:59:04 +0000</pubDate><guid>http://sebastien-han.fr/blog/2019/05/17/Rook-just-landed-on-operatorhub-io/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/rook-operator-framework.png" alt="Rook just landed on operatorhub.io"&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m excited to announce that just right for Cephalocon and KubeCon Europe, Rook has landed on &lt;a href="https://operatorhub.io"&gt;operatorhub.io&lt;/a&gt;.
It has been quite a challenge to have it merged, but in the end &lt;a href="https://github.com/operator-framework/community-operators/pull/348"&gt;my pull request&lt;/a&gt; got merged :).
If you want to know what this means for upstream you should look at this &lt;a href="https://www.redhat.com/en/blog/rook-ceph-storage-operator-now-operatorhubio"&gt;article&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Hey! What's up?!</title><link>http://sebastien-han.fr/blog/2019/05/09/hey-whats-up/</link><pubDate>Thu, 09 May 2019 19:52:55 +0000</pubDate><guid>http://sebastien-han.fr/blog/2019/05/09/hey-whats-up/</guid><description>&lt;p&gt;&lt;img src="https://raw.githubusercontent.com/rook/rook/master/Documentation/media/logo.svg?sanitize=true" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;It has been a long time since I&amp;rsquo;ve been giving updates or even blogging.
Let&amp;rsquo;s take some time here (while being on the plane) to update you on what I&amp;rsquo;m doing these days.&lt;/p&gt;</description></item><item><title>OpenStack and Ceph for Distributed Hyperconverged Edge Deployments</title><link>http://sebastien-han.fr/blog/2019/03/12/OpenStack-and-Ceph-for-Distributed-Hyperconverged-Edge-Deployments/</link><pubDate>Tue, 12 Mar 2019 16:42:48 +0000</pubDate><guid>http://sebastien-han.fr/blog/2019/03/12/OpenStack-and-Ceph-for-Distributed-Hyperconverged-Edge-Deployments/</guid><description>&lt;p&gt;I&amp;rsquo;m simply relaying an article I reviewed and helped writting.
It is reflecting my talk from the last OpenStack Summit in Berlin.&lt;/p&gt;
&lt;p&gt;You can &lt;a href="https://thenewstack.io/openstack-and-ceph-for-distributed-hyperconverged-edge-deployments/"&gt;read it here&lt;/a&gt;
Thanks to the author for capturing the essence of the talk.&lt;/p&gt;</description></item><item><title>The new Ceph container demo is super dope!</title><link>http://sebastien-han.fr/blog/2017/06/27/New-Ceph-container-demo-is-super-dope/</link><pubDate>Tue, 27 Jun 2017 16:41:53 +0000</pubDate><guid>http://sebastien-han.fr/blog/2017/06/27/New-Ceph-container-demo-is-super-dope/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/ceph-demo-container-dope.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;I have been recently working on refactoring our Ceph container images.
We used to have two separate images for &lt;code&gt;daemon&lt;/code&gt; and &lt;code&gt;demo&lt;/code&gt;.
Recently, for Luminous, I decided to merge the demo container into daemon.
It makes everything easier, code is in a single place, we only have a single image to test with the CI and users have a single image to play with.&lt;/p&gt;</description></item><item><title>Ceph Docker better support for Bluestore</title><link>http://sebastien-han.fr/blog/2017/06/14/Ceph-Docker-better-support-for-Bluestore/</link><pubDate>Wed, 14 Jun 2017 11:16:04 +0000</pubDate><guid>http://sebastien-han.fr/blog/2017/06/14/Ceph-Docker-better-support-for-Bluestore/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/better-bluestore-support-container.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;I have been extensively working on &lt;a href="https://github.com/ceph/ceph-docker"&gt;ceph-docker&lt;/a&gt; for the last few months and it&amp;rsquo;s getting better.
With the upcoming arrival of Ceph Luminous (next LTS), Bluestore will be the default backend to store objects.
Thus, I had to spend some time working on improving the support for Bluestore.&lt;/p&gt;</description></item><item><title>Disabling scenarios in ceph-docker</title><link>http://sebastien-han.fr/blog/2017/04/17/Disabling-scenarios-in-ceph-docker/</link><pubDate>Mon, 17 Apr 2017 10:35:34 +0000</pubDate><guid>http://sebastien-han.fr/blog/2017/04/17/Disabling-scenarios-in-ceph-docker/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/ceph-docker-disable-scenarios.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;I recently completed a full resync from Kraken to Jewel in &lt;a href="https://github.com/ceph/ceph-docker"&gt;ceph-docker&lt;/a&gt; in which I introduced a new feature to disable scenarios.
Running an application on bleeding edge technology can be tough and challenging for individuals and also for companies.
Even me, as a developer and for bleeding edge testers I&amp;rsquo;m tempted to release unstable features (understand not recommended for production).
So sometimes it&amp;rsquo;s handy to have the ability to restrict the use of a software by disabling some of its functionality.
This is exactly what I did for ceph-docker, in this article I&amp;rsquo;ll explain how that works.&lt;/p&gt;</description></item><item><title>Test Ceph Luminous pre-release with ceph-docker</title><link>http://sebastien-han.fr/blog/2017/04/13/Testing-Luminous-pre-release-with-ceph-docker/</link><pubDate>Thu, 13 Apr 2017 11:55:17 +0000</pubDate><guid>http://sebastien-han.fr/blog/2017/04/13/Testing-Luminous-pre-release-with-ceph-docker/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/test-pre-release-ceph-luminous-container.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;*&lt;em&gt;/!\ DISCLAIMER /!*&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;*&lt;em&gt;/!\ DO NOT GET TOO EXCITED, AT THE TIME OF THE WRITTING LUMINOUS IS NOT OFFICIALLY RELEASE IN STABLE YET /!*&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;*&lt;em&gt;/!\ USE AT YOUR OWN RISK, DO NOT PUT PRODUCTION DATA ON THIS /!*&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Luminous is just around the corner but we have been having packages available for a couple of weeks already.
That&amp;rsquo;s why I recently thought: &amp;ldquo;how come don&amp;rsquo;t we have any Ceph container image for Luminous then?&amp;rdquo;.
And I know a lot of you are eager to test the latest developments of Bluestore (the new method to store objects, directly on a raw device).&lt;/p&gt;
&lt;p&gt;Now it&amp;rsquo;s done, you can fetch the &lt;code&gt;ceph/daemon&lt;/code&gt; image using one of these two tags:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;tag-build-master-luminous-centos-7&lt;/li&gt;
&lt;li&gt;tag-build-master-luminous-ubuntu-16.04&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And you will get a running Ceph cluster on Luminous.&lt;/p&gt;</description></item><item><title>Debug Ceph Docker containers</title><link>http://sebastien-han.fr/blog/2017/03/27/Debug-Ceph-Docker-containers/</link><pubDate>Mon, 27 Mar 2017 17:00:49 +0000</pubDate><guid>http://sebastien-han.fr/blog/2017/03/27/Debug-Ceph-Docker-containers/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/ceph-docker-debug.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;For the last couple of weeks, &lt;a href="https://github.com/ErwanAliasr1"&gt;Erwan Velu&lt;/a&gt; and I have been busy refactoring the entire &lt;a href="https://github.com/ceph/ceph-docker"&gt;ceph-docker&lt;/a&gt; code base.
Through these cosmetic changes, we implemented new mechanisms to finely grained debug containers at run time.
This article was co-written with Erwan Velu and will explain what we worked on.&lt;/p&gt;</description></item><item><title>Containerize Ceph: store config options in monitor KV store</title><link>http://sebastien-han.fr/blog/2017/02/27/Containerize-Ceph-blueprint-store-ceph-options-in-monitor-kv-store/</link><pubDate>Mon, 27 Feb 2017 14:26:36 +0000</pubDate><guid>http://sebastien-han.fr/blog/2017/02/27/Containerize-Ceph-blueprint-store-ceph-options-in-monitor-kv-store/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/ceph-config-kv-store.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;During the last CDM (Ceph Developer Monthly), I presented a blueprint that will help Ceph playing nicely when it&amp;rsquo;s being containerized.&lt;/p&gt;</description></item><item><title>No more privileged containers for Ceph OSDs</title><link>http://sebastien-han.fr/blog/2017/02/20/No-more-priviledged-containers-for-Ceph-OSDs/</link><pubDate>Mon, 20 Feb 2017 15:45:50 +0000</pubDate><guid>http://sebastien-han.fr/blog/2017/02/20/No-more-priviledged-containers-for-Ceph-OSDs/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/ceph-container-no-more-privilege-mode.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m really sorry for being so quiet lately, I know I promised to release articles more regularly and I clearly failed&amp;hellip;
Many things are going on and where motivation is key to write articles, I&amp;rsquo;ve been having a hard time to find the right motivation to write :/&lt;/p&gt;
&lt;p&gt;However, I am not giving up and I finally found the time to write a little bit on the things we improved in &lt;a href="https://github.com/ceph/ceph-docker"&gt;ceph-docker&lt;/a&gt;, our Ceph in container project.&lt;/p&gt;</description></item><item><title>Devstack Ceph supports containerized Ceph</title><link>http://sebastien-han.fr/blog/2016/10/21/Devstack-Ceph-supports-containerized-Ceph/</link><pubDate>Fri, 21 Oct 2016 15:18:20 +0000</pubDate><guid>http://sebastien-han.fr/blog/2016/10/21/Devstack-Ceph-supports-containerized-Ceph/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/devstack-ceph-container.jpg" alt="Devstack Ceph supports containerized Ceph"&gt;&lt;/p&gt;
&lt;p&gt;Yes people, I&amp;rsquo;m still alive :).
As you might noticed, I&amp;rsquo;ve been having a hard time to keep up the pace with blogging.
It&amp;rsquo;s mainly due to me traveling a lot these days and preparing conferences.
It&amp;rsquo;s a really busy end of the year for me :).&lt;/p&gt;
&lt;p&gt;Fortunately, I&amp;rsquo;m still finding the time to work on some new features to projects I like.
As you might know, I&amp;rsquo;ve been busy working on ceph-ansible and ceph-docker, trying conciliate both and making sure they work well together.
In ceph-docker, we have an interesting container image, that I already presented &lt;a href="http://www.sebastien-han.fr/blog/2015/08/24/ceph-cluster-on-docker-for-testing/"&gt;here&lt;/a&gt;.
I was recently thinking we could use it to simplify the Ceph bootstrapping process in DevStack.
The patch I recently merge doesn&amp;rsquo;t get ride of the &amp;ldquo;old&amp;rdquo; way to bootstrap, the path is just a new addition, a new deployment method.&lt;/p&gt;
&lt;p&gt;In practice, this doesn&amp;rsquo;t change anything for me, but at some point it allows us to validate that a containerized Ceph doesn&amp;rsquo;t have any problem and bring the same functionality as a non-containerized Ceph.
Without further ado, let&amp;rsquo;s jump into this!&lt;/p&gt;</description></item><item><title>Ceph migrate from non-containerized to containerized daemons</title><link>http://sebastien-han.fr/blog/2016/09/26/Ceph-migrate-from-non-containerized-to-containers-daemons/</link><pubDate>Mon, 26 Sep 2016 11:34:57 +0000</pubDate><guid>http://sebastien-han.fr/blog/2016/09/26/Ceph-migrate-from-non-containerized-to-containers-daemons/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/ceph-migrate-non-container-to-container.jpg" alt="Ceph migrate from non-containerized to containerized daemons"&gt;&lt;/p&gt;
&lt;p&gt;Long time no see!
I know, though times at the office, this won&amp;rsquo;t probably stop until Christmas break, so I&amp;rsquo;ll do my best to keep up the pace.
In this article, I will explain how to take over an existing Ceph bare metal deployment and use containers.
Spoiler: Ansible baby, Ansible!&lt;/p&gt;</description></item><item><title>Ceph zap device container</title><link>http://sebastien-han.fr/blog/2016/07/25/Ceph-Zap-device-container/</link><pubDate>Mon, 25 Jul 2016 11:24:43 +0000</pubDate><guid>http://sebastien-han.fr/blog/2016/07/25/Ceph-Zap-device-container/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/zap-device-container.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;Some use cases might require to zap a device (destroy partition tables) prior to run your Ceph OSD container with a dedicated disk.
While running development environment this is particularly interesting as this allows us to quickly bootstrap and tear down sandboxes.&lt;/p&gt;</description></item><item><title>Ceph RBD mirror daemon available in containers</title><link>http://sebastien-han.fr/blog/2016/07/21/RBD-mirror-daemon-available-in-containers/</link><pubDate>Thu, 21 Jul 2016 10:39:15 +0000</pubDate><guid>http://sebastien-han.fr/blog/2016/07/21/RBD-mirror-daemon-available-in-containers/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/rbd-mirror-container.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;I recently pushed into &lt;a href="https://github.com/ceph/ceph-docker"&gt;ceph-docker&lt;/a&gt; the support for thr RBD mirror.
This daemon is responsable for asynchronously replicating RBD images from one cluster to another.
The main purpose of the daemon is to address disaster recovery use cases.&lt;/p&gt;</description></item><item><title>Busy working on ceph-docker :)</title><link>http://sebastien-han.fr/blog/2016/06/06/Busy-working-on-ceph-docker/</link><pubDate>Mon, 06 Jun 2016 20:10:38 +0000</pubDate><guid>http://sebastien-han.fr/blog/2016/06/06/Busy-working-on-ceph-docker/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/ceph-docker-news.jpg" alt="Title"&gt;&lt;/p&gt;
&lt;p&gt;I have been having a hard time keeping up with all things happening at the office and the blog.
One of the main reason is that I actively resumed my work on &lt;a href="https://github.com/ceph/ceph-docker"&gt;ceph-docker&lt;/a&gt;, in this article I will explain some of the things I have been working on.&lt;/p&gt;</description></item><item><title>Ceph cluster on Docker for testing</title><link>http://sebastien-han.fr/blog/2015/08/24/ceph-cluster-on-docker-for-testing/</link><pubDate>Mon, 24 Aug 2015 15:22:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2015/08/24/ceph-cluster-on-docker-for-testing/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/ceph-docker-demo.jpg" alt="Ceph cluster on Docker for testing"&gt;&lt;/p&gt;
&lt;p&gt;I haven&amp;rsquo;t advertised this one really much (even if I&amp;rsquo;ve been using it in some articles).
Since people are still wondering how to quickly get a full Ceph cluster up and running for testing, I believe it deserves its own article so it will get more visibility.
Re-introducing the &lt;a href="https://github.com/ceph/ceph-docker/tree/master/demo"&gt;Ceph demo container&lt;/a&gt;.
This is going to be a really short article :).&lt;/p&gt;</description></item><item><title>Getting started with the Docker RBD volume plugin</title><link>http://sebastien-han.fr/blog/2015/08/17/getting-started-with-the-docker-rbd-volume-plugin/</link><pubDate>Mon, 17 Aug 2015 16:52:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2015/08/17/getting-started-with-the-docker-rbd-volume-plugin/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/docker-ceph-rbd-volume-plugin.jpg" alt="Getting started with the Docker RBD volume plugin"&gt;&lt;/p&gt;
&lt;p&gt;Docker 1.8 was just released a week ago and with it came the support for volume plugin.
Several volume plugins are available but today I will be introducing the Ceph RBD ones (yes there are currently 3 different drivers).&lt;/p&gt;</description></item><item><title>Build Kubernetes from source</title><link>http://sebastien-han.fr/blog/2015/07/01/build-kubernetes-from-source/</link><pubDate>Wed, 01 Jul 2015 16:27:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2015/07/01/build-kubernetes-from-source/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/build-kubernetes-from-source.jpg" alt="Build Kubernetes from source"&gt;&lt;/p&gt;
&lt;p&gt;It is crucial to know how to build Kubernetes from source if you want to implement new features.&lt;/p&gt;</description></item><item><title>Bring persistent storage for your containers with KRBD on Kubernetes</title><link>http://sebastien-han.fr/blog/2015/06/29/bring-persistent-storage-for-your-containers-with-krbd-on-kubernetes/</link><pubDate>Mon, 29 Jun 2015 00:24:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2015/06/29/bring-persistent-storage-for-your-containers-with-krbd-on-kubernetes/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/kubernetes-ceph-krbd.png" alt="Bring persistent storage for your containers with KRBD on Kubernetes"&gt;&lt;/p&gt;
&lt;p&gt;Use RBD device to provide persistent storage to your containers.
This work was initiated by a colleague of mine &lt;a href="https://huaminchen.wordpress.com"&gt;Huamin Chen&lt;/a&gt;.
I would like to take the opportunity to thank him for the troubleshooting session we had.
Having the ability to use persistent volume for your containers is critical, containers can be ephemeral since they are immutable.
If they did on a machine they can be bootstrapped on another host without any problem.
The only problem here is we need to ensure that somehow the data that come with this container will follow it no matter where it goes.
This is exactly what we want to achieve with this implementation.&lt;/p&gt;</description></item><item><title>Map a RBD device inside a Docker container</title><link>http://sebastien-han.fr/blog/2015/06/26/map-a-rbd-device-inside-a-docker-container/</link><pubDate>Fri, 26 Jun 2015 16:11:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2015/06/26/map-a-rbd-device-inside-a-docker-container/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/map-rbd-device-inside-docker-container.jpg" alt="Map a RBD device inside a Docker container"&gt;&lt;/p&gt;
&lt;p&gt;People have been having trouble to map a RBD device in a container.
Quick tip on how to map a Rados Block Device into a container.&lt;/p&gt;</description></item><item><title>Bootstrap your Ceph cluster in Docker</title><link>http://sebastien-han.fr/blog/2015/06/23/bootstrap-your-ceph-cluster-in-docker/</link><pubDate>Tue, 23 Jun 2015 00:17:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2015/06/23/bootstrap-your-ceph-cluster-in-docker/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/bootstrap-ceph-cluster-docker.jpg" alt="Bootstrap your Ceph cluster in Docker"&gt;&lt;/p&gt;
&lt;p&gt;Almost two years have passed since my first attempt to &lt;a href="http://www.sebastien-han.fr/blog/2013/09/19/how-I-barely-got-my-first-ceph-mon-running-in-docker/"&gt;run Ceph inside Docker&lt;/a&gt;.
Time has elapsed and I haven&amp;rsquo;t really got the time to resume this work until recently.
For the last couple of months, I have been devoting a third part of my time to contributing on deploying &lt;a href="https://github.com/ceph/ceph-docker"&gt;Ceph in Docker&lt;/a&gt;.
Before we start, I would like to highlight that nothing of this work would have been possible without the help of &lt;a href="http://www.cycoresys.com"&gt;Seán C. McCord&lt;/a&gt;.
Indeed the current ceph-docker repository is based on Seán&amp;rsquo;s initial work.
Let&amp;rsquo;s see how you can get this running!&lt;/p&gt;</description></item><item><title>Deploy Ceph monitors on Kubernetes</title><link>http://sebastien-han.fr/blog/2015/06/18/deploy-ceph-monitors-on-kubernetes/</link><pubDate>Thu, 18 Jun 2015 14:56:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2015/06/18/deploy-ceph-monitors-on-kubernetes/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/deploy-ceph-monitors-kubernetes.jpg" alt="Deploy Ceph monitors on Kubernetes"&gt;&lt;/p&gt;
&lt;p&gt;As part of my work on &lt;a href="https://github.com/ceph/ceph-docker"&gt;ceph-docker&lt;/a&gt;, I have been playing a bit with Kubernetes.
As a first exercise, I thought it would be interesting to run my Ceph monitors with Kubernetes.
Let&amp;rsquo;s see how we can achieve that.&lt;/p&gt;</description></item><item><title>Crash course: next generation servers with containers</title><link>http://sebastien-han.fr/blog/2014/02/03/crash-course-next-generation-servers-with-containers/</link><pubDate>Mon, 03 Feb 2014 14:40:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2014/02/03/crash-course-next-generation-servers-with-containers/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/next-gen-serv-with-containers.jpg" alt="Crash course: next generation servers with containers"&gt;&lt;/p&gt;
&lt;p&gt;For more than a year, containers have become more and more popular especially thanks to rise of Docker.
Unfortunately the concept itself is not always clear for everyone.
It is important to understand the difference between LXC and Docker.
In this article, I will expose the different technologies available.&lt;/p&gt;</description></item><item><title>Access a Docker container without ssh</title><link>http://sebastien-han.fr/blog/2014/01/27/access-a-container-without-ssh/</link><pubDate>Mon, 27 Jan 2014 00:01:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2014/01/27/access-a-container-without-ssh/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/docker-nsenter.jpg" alt="Access a Docker container without ssh"&gt;&lt;/p&gt;
&lt;p&gt;Quick tip to access a container without SSH.&lt;/p&gt;</description></item><item><title>Docker at Spotify</title><link>http://sebastien-han.fr/blog/2014/01/10/docker-at-spotify/</link><pubDate>Fri, 10 Jan 2014 09:58:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2014/01/10/docker-at-spotify/</guid><description>&lt;p&gt;Nice talk from Rohan Singh about the internal usage of Docker at &lt;a href="https://www.spotify.com/"&gt;Spotify&lt;/a&gt;.&lt;/p&gt;
&lt;div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"&gt;
 &lt;iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/pts6F00GFuU?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"&gt;&lt;/iframe&gt;
 &lt;/div&gt;</description></item><item><title>How I barely got my first Ceph monitor running in Docker</title><link>http://sebastien-han.fr/blog/2013/09/19/how-I-barely-got-my-first-ceph-mon-running-in-docker/</link><pubDate>Thu, 19 Sep 2013 22:37:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2013/09/19/how-I-barely-got-my-first-ceph-mon-running-in-docker/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/docker-ceph-mon.jpg" alt="Your first ceph-mon with Docker"&gt;&lt;/p&gt;
&lt;p&gt;Docker is definitely the new trend. Thus I quickly wanted to try to put a Ceph monitor inside a Docker container. Story of a tough journey&amp;hellip;&lt;/p&gt;</description></item><item><title>First glimpse at CoreOS</title><link>http://sebastien-han.fr/blog/2013/09/03/first-glimpse-at-coreos/</link><pubDate>Tue, 03 Sep 2013 00:10:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2013/09/03/first-glimpse-at-coreos/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/coreos.png" alt="First step with CoreOS"&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://coreos.com/"&gt;CoreOS&lt;/a&gt; is an emergent project that aims to address one of the most pressing questions in the server&amp;rsquo;s world.
We at eNovance, therefore released eDeploy: a tool that performs bare metal deployment and manages upgrades with ease.
Deploying and upgrading servers are currently two major concerns in the IT world since none (or at least very few people know how to do).
I couldn&amp;rsquo;t resist trying CoreOS.&lt;/p&gt;</description></item><item><title>Introduction à Juju avec LXC</title><link>http://sebastien-han.fr/blog/2012/02/07/introduction-a-juju-avec-lxc/</link><pubDate>Tue, 07 Feb 2012 17:14:00 +0000</pubDate><guid>http://sebastien-han.fr/blog/2012/02/07/introduction-a-juju-avec-lxc/</guid><description>&lt;p&gt;&lt;img src="http://sebastien-han.fr/images/juju-logo.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Juju fait parti des nouveaux outils développés par Ubuntu dans sa gamme Ubuntu Cloud pour déployer votre infrastructure Cloud privé. Il fait parti intégrante du projet Orchestra. Actuellement Juju est en cours de développement. Il est toutefois possible de réaliser des tests soit avec des instances Amazon EC2 soit en local avec des LXC. Pour ma part j&amp;rsquo;ai testé cela à partir de conteneur LXC.&lt;/p&gt;</description></item></channel></rss>