# Re-bootstrap data container in a split setup?

**URL:** <https://meta.discourse.org/t/re-bootstrap-data-container-in-a-split-setup/27893>\
**Category:** Product Support\
**Created:** [24. April 2015 um 06:38 UTC](https://meta.discourse.org/t/re-bootstrap-data-container-in-a-split-setup/27893 "2015-04-24T06:38:32Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![calmh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/calmh/32/115466_2.png) [@calmh](https://meta.discourse.org/u/calmh)\
**Post date:** [24. April 2015 um 06:38 UTC](https://meta.discourse.org/t/re-bootstrap-data-container-in-a-split-setup/27893/1 "2015-04-24T06:38:32Z")

</div>

I’m running a split setup (data and web\_only containers). This makes it easy and quick to update the web container with minimal downtime. 👍

However, I noticed today that the web container I’m running is based on `samsaffron/discourse 1.0.10` while the data container is based on `samsaffron/discourse 1.0.6`. Presumably, at some point, it would be a good idea to update the data container as well.

What’s the recommended process there? Shut down the web container, destroy, bootstrap and launch a new data container, then launch the web container again? Are there any gotchas related to the update, in terms of not screwing up my data…?

---

_[View the full topic](https://meta.discourse.org/t/re-bootstrap-data-container-in-a-split-setup/27893)._