# 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:** [14 september 2015 om 07: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:** 15

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [23 september 2015 om 04:54 UTC](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205/15 "2015-09-23T04:54:09Z")

</div>

> [@fbender](#):
>
> Oh wow, hit some limit and had to wait 20 hours before I could answer. Is that the Discourse default or specific to this installation?

Working as designed: you’re heavily ratelimited in the first 24 hours after you create your account.

> [@fbender](#):
>
> With a git(hub) hook, the try-discourse image can be created automatically whenever a new Discourse version is released

I don’t think that’s feasible to do on every commit (remember, you can follow the tests-passed branch) - the Docker images are pretty big. Probably better to keep the image updates to major releases + dependency changes.

(Also remember that the rebuild/bootstrap operation _creates a new Docker image_, just for you.)

---

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