<p>If it's just the master, I would say it's okay. The main concern would be any recursive dependencies where your CI tool manages the Docker platform that it runs on. </p>

<p>Build agents are another case. I've run CI with Docker in both configurations, and I prefer running outside of Docker and invoking it during your build, as it allows consistency between your dev and CI platform. Eg: <a href="https://github.com/amaysim-au/docker-serverless" rel="nofollow noreferrer">https://github.com/amaysim-au/docker-serverless</a></p>

CC BY-SA 3.0
2017-09-22T05:48:18.133Z
2017-09-22T05:48:18.133Z
user2640621
<p><strong>Pros</strong></p>

<ul>
<li>possible to run the CI on a container orchestration platform</li>
</ul>

<p><strong>Cons</strong></p>

<ul>
<li>docker in docker in docker</li>
</ul>

CC BY-SA 3.0
2017-09-23T18:43:41.143Z
The poster didn't make mention of having executors on master.
Matt O.
CC BY-SA 3.0
2017-09-21T16:21:19.073Z
2017-09-21T16:21:19.073Z
030
<p>Carrying on from <a href="https://devops.stackexchange.com/questions/2103/what-os-should-a-master-node-ci-virtual-machine-be">this</a> question, would you want to dockerise your CI (Gitlab (especially if Gitlab also contains all your repositories) or Jenkins) installation on your master node virtual machine?</p>

<p>What are the advantages and disadvantages to this, than just installing normally onto the VM without docker?</p>

<docker><continuous-integration>
Dockerize CI installation on master node VM
Rekovni
# Dockerize CI installation on master node VM

(Asked by: username_0 on 2017-09-21)

Carrying on from [this](https://devops.stackexchange.com/questions/2103/what-os-should-a-master-node-ci-virtual-machine-be) question, would you want to dockerise your CI (Gitlab (especially if Gitlab also contains all your repositories) or Jenkins) installation on your master node virtual machine?

What are the advantages and disadvantages to this, than just installing normally onto the VM without docker?

**Tags:** docker, continuous-integration


---

## 2 answers

### Answer by username_2 on 2017-09-21. Score: 3 | Accepted answer

**Pros**

* possible to run the CI on a container orchestration platform

**Cons**

* docker in docker in docker

> **Comments:**
> **username_3**: The poster didn't make mention of having executors on master.  

---

### Answer by username_1 on 2017-09-22. Score: 3

If it's just the master, I would say it's okay. The main concern would be any recursive dependencies where your CI tool manages the Docker platform that it runs on.

Build agents are another case. I've run CI with Docker in both configurations, and I prefer running outside of Docker and invoking it during your build, as it allows consistency between your dev and CI platform. Eg: <https://github.com/amaysim-au/docker-serverless>


---

