# Persistent configuration of restart-policy

**URL:** <https://meta.discourse.org/t/persistent-configuration-of-restart-policy/213715>\
**Category:** Self-hosting\
**Created:** [January 3, 2022, 1:32pm UTC](https://meta.discourse.org/t/persistent-configuration-of-restart-policy/213715 "2022-01-03T13:32:19Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [January 3, 2022, 7:56pm UTC](https://meta.discourse.org/t/persistent-configuration-of-restart-policy/213715/2 "2022-01-03T19:56:56Z")

</div>

I don’t remember anyone else ever asking this, and I don’t see an obvious way. I think your best bet is do to a

```
  ./launcher destroy app

```

if you want it to stay stopped and start it again with

```
  ./launcher start app

```

This will destroy the container, so any changes you’ve made inside it (like upgrades from `docker_manager`) will be destroyed.

Oh, but here’s this:

> <https://stackoverflow.com/questions/26852321/docker-add-a-restart-policy-to-a-container-that-was-already-created>

tl;dr: do a `docker update --restart=unless-stopped app` after each rebuild.

---

_[View the full topic](https://meta.discourse.org/t/persistent-configuration-of-restart-policy/213715)._