# Can't start development instance-- renice: failed to set priority

**URL:** <https://meta.discourse.org/t/cant-start-development-instance-renice-failed-to-set-priority/265375>\
**Category:** Development\
**Created:** [May 17, 2023, 6:35pm UTC](https://meta.discourse.org/t/cant-start-development-instance-renice-failed-to-set-priority/265375 "2023-05-17T18:35:41Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [May 19, 2023, 7:58am UTC](https://meta.discourse.org/t/cant-start-development-instance-renice-failed-to-set-priority/265375/3 "2023-05-19T07:58:11Z")

</div>

An update to the docker image could have included an update to utilities such as renice. Or some kind of policy update within the container might have got in the way, if for example different UIDs are used for different processes in different ways. Or possibly the base priority has changed so the renice is now trying to increase priority, which it can’t do.

---

_[View the full topic](https://meta.discourse.org/t/cant-start-development-instance-renice-failed-to-set-priority/265375)._