# Can Discourse ship frequent Docker images that do not need to be bootstrapped?

**URL:** https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205
**Category:** Development
**Created:** [9월 14, 2015, 7:01오전 UTC](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205 "2015-09-14T07:01:52Z")
**Posts on this page:** 1
**Showing post:** 80

<div class="post-metadata">

### Author: ![jayfk](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@jayfk](https://meta.discourse.org/u/jayfk)
#### Post date: [10월 11, 2016, 8:12오전 UTC](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205/80 "2016-10-11T08:12:32Z")

</div>

> [@sam](#):
>
> As it stands our self installers can install latest and update to latest by running one command. This compose based installation has no bootstrapping phase so
> 
> [snip]

The idea is to ship a bash script that runs docker-compose under the hood and is doing the install/upgrade/whatnot.

> [@sam](#):
>
> If you start sharing directories between the NGINX and unicorn containers then you start violating the Docker purity rules so… “best practice” ends up being slower.

That’s simply not true. You can share volumes just fine.

> [@sam](#):
>
> I just don’t see this as an improvement over what we have now.

Because you live and breathe the code you wrote there.

Let’s put this in another perspective: Say I’ve just found out about ruby and want to write my own website. Instead of using RoR I’m writing my own thing that implements a WSGI subset and speaks directly to nginx. It works perfect, is extremely performant and easy to use for end users, but nobody ever understands what I wrote there.

It’s the same thing here. Instead of using something like docker-compose you wrote your own thing. That’s totally fine and was probably the right thing to do at this time. But really, only the team actively working on it understands what’s going on.

It basically comes down to: Do you want to take the longer road that people understand by using established tools, or do you prefer to use well working shortcuts nobody is able to follow (except the team) by writing your own thing?

Again, I totally understand why you did it this way. If you ever prefer to go down the docker-compose route, @ping me at GitHub and I’ll make sure to help you out with all roadblocks you might encounter.

---

_[View the full topic](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205)._