# Custom Docker-Discourse bootstrapping from private GIT repository **URL:** \ **Category:** Self-hosting\ **Created:** [06.Июль.2015 12:34:54 UTC](https://meta.discourse.org/t/custom-docker-discourse-bootstrapping-from-private-git-repository/30822 "2015-07-06T12:34:54Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![RabidFX](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rabidfx/32/114395_2.png) [@RabidFX](https://meta.discourse.org/u/RabidFX)\ **Post date:** [06.Июль.2015 12:34:54 UTC](https://meta.discourse.org/t/custom-docker-discourse-bootstrapping-from-private-git-repository/30822/1 "2015-07-06T12:34:54Z")
Hello all o/ I’m working on a custom theme for Discourse. Everything works well in the Vagrant VM, and it’s now time to try a “real” install. I pulled the standard Docker image and modified the templates so the bootstrapping would pull from my fork of the **discourse/discourse** repo, and not the original. Thing is, the repo I will pull from uses SSH key authentication for the all users, including **git**. As expected, it fails on bootstrapping with the following message: ``` I, [2015-07-06T12:25:59.424104 #36] INFO -- : > cd /var/www/discourse && git fetch custom-origin release Host key verification failed. fatal: Could not read from remote repository. ``` **How can I pull from a private repo expecting a key when bootstrapping?** If the alternative is easier: this repo is hosted on the docker host machine itself. So I could also read directly from the container in the host filesystem… But I assume this is harder than SSHing in, this being a possible Docker security hole… --- _[View the full topic](https://meta.discourse.org/t/custom-docker-discourse-bootstrapping-from-private-git-repository/30822)._