# Is RESIN\_APP\_RESTART\_RETRIES still valid?

**URL:** <https://forums.balena.io/t/is-resin-app-restart-retries-still-valid/103928>\
**Category:** Product support\
**Created:** [May 1, 2020, 5:46pm UTC](https://forums.balena.io/t/is-resin-app-restart-retries-still-valid/103928 "2020-05-01T17:46:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrjogo](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mrjogo/32/2646_2.png) [@mrjogo](https://forums.balena.io/u/mrjogo)\
**Post date:** [May 1, 2020, 5:46pm UTC](https://forums.balena.io/t/is-resin-app-restart-retries-still-valid/103928/1 "2020-05-01T17:46:25Z")

</div>

I’m trying to prevent any of my services from going into reboot loops, but limiting restarts was only added in docker compose format version 3. I found the following reference to `RESIN_APP_RESTART_RETRIES` to do the same thing: [I've just tried to deploy a Tomcat alpine container and I may have broken your workers](https://forums.balena.io/t/ive-just-tried-to-deploy-a-tomcat-alpine-container-and-i-may-have-broken-your-workers/906/17). However, the referenced issue to add it to the documentation ([https://github.com/balena-io/docs/issues/500](https://github.com/balena-io/docs/issues/500)) was closed without it ever being added.

I’m wondering whether it was just never added, or is no longer a valid configuration variable, and if it is valid, whether it works on multicontainer deploys.

Thanks!

---

<div class="post-metadata">

**Author:** ![garethtdavies](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/garethtdavies/32/2669_2.png) [@garethtdavies](https://forums.balena.io/u/garethtdavies)\
**Post date:** [May 1, 2020, 5:59pm UTC](https://forums.balena.io/t/is-resin-app-restart-retries-still-valid/103928/4 "2020-05-01T17:59:52Z")

</div>

Hi, all the valid configuration values are available here [https://www.balena.io/docs/learn/manage/configuration/#variable-list](https://www.balena.io/docs/learn/manage/configuration/#variable-list). So `RESIN_APP_RESTART_RETRIES ` is no longer valid. I did look to see when this was updated and looks like it was removed in the update to multicontainer.

---

<div class="post-metadata">

**Author:** ![mrjogo](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mrjogo/32/2646_2.png) [@mrjogo](https://forums.balena.io/u/mrjogo)\
**Post date:** [May 1, 2020, 6:28pm UTC](https://forums.balena.io/t/is-resin-app-restart-retries-still-valid/103928/6 "2020-05-01T18:28:09Z")

</div>

Thanks. Then I guess the follow-up question is what is the current way to limit restart retries to prevent reboot loops?

---

<div class="post-metadata">

**Author:** ![srlowe](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/srlowe/32/2638_2.png) [@srlowe](https://forums.balena.io/u/srlowe)\
**Post date:** [May 4, 2020, 10:49am UTC](https://forums.balena.io/t/is-resin-app-restart-retries-still-valid/103928/14 "2020-05-04T10:49:03Z")

</div>

Hello, unfortunately there’s balena supported approach for this exactly. If not restarting containers at all is an acceptable solution, then you could use the “no” option for restart policy: [https://docs.docker.com/compose/compose-file/#restart](https://docs.docker.com/compose/compose-file/#restart) This is an area that will be looked at relatively soon though, and so there may be a better solution in the future.