# How to inject files/commands into Docker bootstrap process?

**URL:** <https://meta.discourse.org/t/how-to-inject-files-commands-into-docker-bootstrap-process/24106>\
**Category:** Self-hosting\
**Created:** [Janvier 16, 2015, 11:01 UTC](https://meta.discourse.org/t/how-to-inject-files-commands-into-docker-bootstrap-process/24106 "2015-01-16T23:01:55Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![kpfleming](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kpfleming/32/116414_2.png) [@kpfleming](https://meta.discourse.org/u/kpfleming)\
**Post date:** [Janvier 16, 2015, 11:01 UTC](https://meta.discourse.org/t/how-to-inject-files-commands-into-docker-bootstrap-process/24106/1 "2015-01-16T23:01:55Z")

</div>

I’m setting up a Discourse install using the Docker-based instructions; this is being done on a weird internal corporate network, that has both HTTP/HTTPS proxies _and_ has a custom CA root certificate.

I’ve edited app.yml to add the http\_proxy/https\_proxy environment variables that are necessary to run Git to pull ‘pups’, but there don’t seem to be any provisions for injecting additional files (and commands to run) before that command is run. I’ll need to push a file into the container, add a line into a configuration file, and run ‘update-ca-certificates’ before the Git installation inside the container will be able to pull from an HTTPS connection to Github.

Alternatively, I could set Git’s global configuration in the container to disable SSL certificate verification, and I’ll probably edit the launcher script to do that as a temporary workaround. Just figured I’d post this here to record the situation, other people may run into a need for pushing additional files or commands into the container during the bootstrap.

---

_[View the full topic](https://meta.discourse.org/t/how-to-inject-files-commands-into-docker-bootstrap-process/24106)._