<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>docker on batmat.net</title>
		<link>https://batmat.net/tags/docker/</link>
		<description>Recent content in docker on batmat.net</description>
		<generator>Hugo</generator>
		<language>fr-FR</language>
		
		
		
		
			<lastBuildDate>Fri, 07 Sep 2018 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://batmat.net/tags/docker/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>How to run and upgrade Jenkins using the official Docker image</title>
				<link>https://batmat.net/2018/09/07/how-to-run-and-upgrade-jenkins-using-the-official-docker-image/</link>
				<pubDate>Fri, 07 Sep 2018 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2018/09/07/how-to-run-and-upgrade-jenkins-using-the-official-docker-image/</guid>
				
				<description> For some time now, I’ve been trying to follow and answer questions arising in the official Git repository for the Docker image of Jenkins.&#xA;I have especially been trying to encourage people to move away from using bind mounts [1] and prefer volumes instead.&#xA;Running Docker Containers Ideally, you never restart a container. You just start a new one from the same (or another) image.&#xA;Anything you want to keep has to be in the declared volume(s), that is all you need.&#xA;</description>
			</item>
			<item>
				<title>Do not run your tests in Continuous Integration with the root user</title>
				<link>https://batmat.net/2017/01/30/do-not-run-your-tests-in-continuous-integration-with-the-root-user/</link>
				<pubDate>Mon, 30 Jan 2017 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2017/01/30/do-not-run-your-tests-in-continuous-integration-with-the-root-user/</guid>
				
				<description> I was working recently on diagnosing unexpected tests failures that were only happening on our brand new Jenkins environment, and weren’t happening on the previous one. To provide some context, we now run a majority of things in one shot Docker containers, and that helped reveal an interested issue.&#xA;The offending code We have a test to check our code behaviour if a file we need to backup is readable or not. It was roughly like the following:&#xA;</description>
			</item>
			<item>
				<title>Upgrading Centos 7 Kernel to enable using Overlay with Docker</title>
				<link>https://batmat.net/2015/10/05/upgrading-centos-7-kernel-to-enable-using-overlay-with-docker/</link>
				<pubDate>Mon, 05 Oct 2015 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2015/10/05/upgrading-centos-7-kernel-to-enable-using-overlay-with-docker/</guid>
				
				<description> Context I wanted to use Overlay storage driver for our Docker hosts (see why devicemapper should be avoided in my opinion. ).&#xA;The issue is: Overlayfs support has been merged in the Linux Kernel in 3.18 and Centos 7 is currently using a 3.10 one .[1].&#xA;Upgrade your kernel Hence, since this is not for a customer-facing production machine, I decided to upgrade the kernel.&#xA;The simplest way to do it is to use ELRepo and install the package called &amp;#39;kernel-ml&amp;#39; (like in kernel mainline).&#xA;</description>
			</item>
			<item>
				<title>Docker Storage Driver: Don&#39;t Use Devicemapper</title>
				<link>https://batmat.net/2015/08/26/docker-storage-driver-dont-use-devicemapper/</link>
				<pubDate>Wed, 26 Aug 2015 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2015/08/26/docker-storage-driver-dont-use-devicemapper/</guid>
				
				<description> DISCLAIMER: I’m not a system expert. What follows is more an aggregation of things I’ve tried and informations gathered on the Internet. I also wrote it to serve as a placeholder for myself. I make sure to provide many links so that you can make your own opinion. Please don’t hesitate to give feedback if you disagree with some statements below.&#xA;For some months now, we’ve started deploying more and more Docker services internally to progressively gather experiences.&#xA;</description>
			</item>
			<item>
				<title>De l&#39;intérêt de Docker pour tout développeur !</title>
				<link>https://batmat.net/2014/10/02/de-linteret-de-docker-pour-tout-developpeur/</link>
				<pubDate>Thu, 02 Oct 2014 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2014/10/02/de-linteret-de-docker-pour-tout-developpeur/</guid>
				
				<description>Dans l&amp;rsquo;article qui suit, je vais vous montrer comment j&amp;rsquo;ai récemment eu l&amp;rsquo;occasion d&amp;rsquo;utiliser Docker pour un cas concret.&#xA;La particularité ici est que cela était un cas utile à un travail de développement : cela n&amp;rsquo;avait pas pour but de faire tourner une application, simplement d&amp;rsquo;accéder à un environnement (via Docker, donc), de récupérer des informations, puis de jeter.&#xA;Pour ce cas, j&amp;rsquo;estime avoir gagné au bas mot plusieurs dizaines de minutes.&#xA;</description>
			</item>
	</channel>
</rss>
