# Supervisor missing in pre-build image?

**URL:** <https://forums.balena.io/t/supervisor-missing-in-pre-build-image/2399>\
**Category:** Product support\
**Created:** [January 14, 2018, 10:01am UTC](https://forums.balena.io/t/supervisor-missing-in-pre-build-image/2399 "2018-01-14T10:01:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![camueller](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/camueller/32/744_2.png) [@camueller](https://forums.balena.io/u/camueller)\
**Post date:** [January 14, 2018, 10:01am UTC](https://forums.balena.io/t/supervisor-missing-in-pre-build-image/2399/1 "2018-01-14T10:01:18Z")

</div>

I installed the pre-build resin-os image without modification (no WiFi required) and therefore without resin-cli.  
I can pull docker images and launch containers but they are not restarted after rebuild. On this forum I read that container restarts are handled by the resin supervisor which should be listening on port 48484 according to [https://resin.io/engineering/introducing-and-open-sourcing-the-resin-supervisor-v1-and-its-api](https://resin.io/engineering/introducing-and-open-sourcing-the-resin-supervisor-v1-and-its-api) . However, there is no process listening on that port.  
What do I have to do to get the supervisor running?

Axel

---

<div class="post-metadata">

**Author:** ![alisondavis17](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/alisondavis17/32/208_2.png) [@alisondavis17](https://forums.balena.io/u/alisondavis17)\
**Post date:** [January 16, 2018, 5:37pm UTC](https://forums.balena.io/t/supervisor-missing-in-pre-build-image/2399/2 "2018-01-16T17:37:02Z")

</div>

Hi @camueller, you may want to post your question in [https://forums.balena.io/c/troubleshooting](https://forums.balena.io/c/troubleshooting), you’re likely to get a faster response from our engineers there 🙂

---

<div class="post-metadata">

**Author:** ![camueller](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/camueller/32/744_2.png) [@camueller](https://forums.balena.io/u/camueller)\
**Post date:** [January 16, 2018, 5:52pm UTC](https://forums.balena.io/t/supervisor-missing-in-pre-build-image/2399/3 "2018-01-16T17:52:05Z")

</div>

Hi @alisondavis17, thanks for the hint - I changed the category accordingly.

---

<div class="post-metadata">

**Author:** ![pimterry](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/pimterry/32/140_2.png) [@pimterry](https://forums.balena.io/u/pimterry)\
**Post date:** [January 18, 2018, 11:46am UTC](https://forums.balena.io/t/supervisor-missing-in-pre-build-image/2399/13 "2018-01-18T11:46:42Z")

</div>

Hi @camueller - the supervisor only runs and manages your containers for you on [Resin.io](http://Resin.io) images, not plain ResinOS. ResinOS gives you the tools to do so yourself, and to directly manage docker on the device any way you’d like, but doesn’t automatically do so for you.

To automatically manage containers on your device, you’ll want to either set up a full [resin.io](http://resin.io) device (which is totally free, for up to 10 devices), or build your own scripts that talk to docker to do so. The resin supervisor is open source ([https://github.com/resin-io/resin-supervisor](https://github.com/resin-io/resin-supervisor)) so you’re welcome to use that for inspiration, but I’m not aware of any way to run it directly without using [resin.io](http://resin.io), as it expects to be able to talk to the resin api.

We are definitely interested in bringing these closer together in future, to provide more of that managed device functionality to [non-Resin.io](http://non-Resin.io) users where we can, but that’s still a way away I’m afraid.