<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitLab Runner on nidomiro</title><link>https://nidomiro.de/tags/gitlab-runner/</link><description>Recent content in GitLab Runner on nidomiro</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 14 Mar 2025 10:43:41 +0100</lastBuildDate><atom:link href="https://nidomiro.de/tags/gitlab-runner/index.xml" rel="self" type="application/rss+xml"/><item><title>More secure DinD in GitLab CI</title><link>https://nidomiro.de/article/more-secure-dind-in-gitlab-ci/</link><pubDate>Thu, 31 Dec 2020 12:00:00 +0000</pubDate><guid>https://nidomiro.de/article/more-secure-dind-in-gitlab-ci/</guid><description>&lt;p>If you are reading this article you probably already know how to use DinD (DockerInDocker) in GitLab CI. The default way is to set &lt;code>privileged=true&lt;/code> in your Runner-config.&lt;/p>
&lt;p>This little flag makes everything work; but at the cost of security. There are many articles regarding this topic, eg. &lt;a href="https://www.trendmicro.com/en_us/research/19/l/why-running-a-privileged-container-in-docker-is-a-bad-idea.html">this one&lt;/a>. The baseline is, if you run a container privileged, and the container uses the root-user inside, you can lose the whole server.&lt;/p></description></item></channel></rss>