# New device image - missing the resin-supervisor image

**URL:** <https://forums.balena.io/t/new-device-image-missing-the-resin-supervisor-image/570>\
**Category:** Product support\
**Created:** [February 9, 2017, 11:10pm UTC](https://forums.balena.io/t/new-device-image-missing-the-resin-supervisor-image/570 "2017-02-09T23:10:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmoss](https://avatars.discourse-cdn.com/v4/letter/c/9e8a1a/32.png) [@cmoss](https://forums.balena.io/u/cmoss)\
**Post date:** [February 9, 2017, 11:10pm UTC](https://forums.balena.io/t/new-device-image-missing-the-resin-supervisor-image/570/1 "2017-02-09T23:10:06Z")

</div>

We’ve just managed to get our new resinos image (based on a 4.4 kernel, with a number of custom modules we need) built for our hardware, and the provisioning seemed to work well, except that for some reason the supervisor docker image wasn’t loaded. By executing the update-resin-supervisor script the image was pulled successfully, and then a resin-connectable -s got everything started and connected to resin.

Is there anything we need to watch out for in our yocto recipes to ensure that we’re including the correct supervisor image in the build?

Thanks!

---

<div class="post-metadata">

**Author:** ![pcarranzav](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/pcarranzav/32/94_2.png) [@pcarranzav](https://forums.balena.io/u/pcarranzav)\
**Post date:** [February 9, 2017, 11:23pm UTC](https://forums.balena.io/t/new-device-image-missing-the-resin-supervisor-image/570/2 "2017-02-09T23:23:40Z")

</div>

Hi @cmoss, I think these are the relevant settings: [https://github.com/resin-os/meta-resin#resin\_connectable--1-default](https://github.com/resin-os/meta-resin#resin_connectable--1-default)

So you’d have to ensure RESIN\_CONNECTABLE and RESIN\_CONNECTABLE\_ENABLE\_SERVICES are set to “1”. Did you change any of those? Or TARGET\_REPOSITORY?

---

<div class="post-metadata">

**Author:** ![open-nandra](https://avatars.discourse-cdn.com/v4/letter/o/c4cdca/32.png) [@open-nandra](https://forums.balena.io/u/open-nandra)\
**Post date:** [February 10, 2017, 9:25am UTC](https://forums.balena.io/t/new-device-image-missing-the-resin-supervisor-image/570/3 "2017-02-10T09:25:13Z")

</div>

Thanks pablo,

one additional question (I’m working on new device with cmoss ;)). We’re using 4.4.48 stable kernel but in this version aufs patches cannot be applied (due to the changes in mm/mmap.c). It works fine in 4.4 kernel though. Some fixes for mmap was introduced in 4.4.2 and this is the reason why patch fails. I was thinking about adapting patch and somehow inject it but it seems to be an overkill (as everything is done in kernel-resin.bbclass. Any other ideas how to solve this issue? Thanks a lot.

Marek

---

<div class="post-metadata">

**Author:** ![imrehg](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/imrehg/32/36_2.png) [@imrehg](https://forums.balena.io/u/imrehg)\
**Post date:** [February 13, 2017, 7:18pm UTC](https://forums.balena.io/t/new-device-image-missing-the-resin-supervisor-image/570/4 "2017-02-13T19:18:56Z")

</div>

Perhaps naively, but would it work if you’d update `kernel-resin.bbclass` for the [4.4 kernel’s aufs patch commit ID](https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/classes/kernel-resin.bbclass#L412) to the latest one for the `aufs4.4` branch on the [aufs-standalone repo](https://github.com/sfjro/aufs4-standalone)? (that is `cc5cfb9aa9bdb2986d24bf7b95fa594a88b1c5f8` at the moment, I think). Just a thought, because I’ve seen that there were a few changes since then on that branch.