Fastest way to dev on local device


Is there a faster way to do local dev than making changes locally on my IDE then pushing to the local device to test? No way to somehow mount my local folder to the local device?



Hi @brice I believe that using the resin cli would be what you are looking for:

Is that what you were looking for?


@floion thanks, it does help but I was looking for something where I could leverage things like hot reload / auto rebuild with watch folders.


I guess you could use inotify in a script to watch your directory and then trigger a resin sync to your device.

Also, just a heads-up in case you did not know about it, there is another development mode you could use, local mode, not sure if it fits better for you than the inotify + resin ssh approach:


Is their an update on this?

The resin-sync takes 30s and that is to long for efficient development. Normally I develop my auto syncing files to the pi and restart the node process in the ssh terminal of the device. This takes less then 4s.

Is their a way to do this on a local development build? Or are their other development options that take less then 5s to test if code is working?


@brett resin sync is different from resin local.
Did you check the link that florin pasted above?
Resin local is a lot faster and might be a good match for your development needs.


I cant find a clear tutorial on how to use the resin local push command.
It first complains that their is no docker file, then I create one by removing .template extension, then i get different errors.
And if I google it I find only open github tickets complaining about the issue.
So I’m a bit lost on that route.


Hi @brett, what does it complain about in the second case using a Dockerfile? In that case the in the FROM statement you have to use a specific image, a valid image name (in practice it means replacing the %%RESIN_MACHINE_NAME%% with your machine, e.g. raspberrypi3 if using an RPi3 or as it’s appropriate, see our list of images, for example: ). We are working on making the CLI work with Dockerfile.template files as well, but it’s in progress (github issue)

Most of the guidance how to use it is in resin local push --help, have some explanation and examples.


Hi thank you for the help so far. But it still isn’t working.
My application works if push to resin and if I use resin sync.

I copied the docker template and replaced the image name as described above. But if I run "git local push deviceuuid -s . " it starts by pulling the container but fails during building. And that is weird since it works for the cloud build and the sync build.

Logs below

$ sudo resin local push mydeviceuuid.local -s . ‹system›

  • Building…
  • Stopping and Removing any previous ‘myappname’ container
  • Building new ‘myappname’ image
    Step 1/11 : FROM resin/raspberrypi3-node:slim
    slim: Pulling from resin/raspberrypi3-node
    5ec7d30a9a8c: Already exists
    2c5f1d9670fa: Already exists
    effee8c83224: Already exists
    9c72b15ef569: Already exists
    8b21541bbf83: Already exists
    5f6f3e4aab84: Already exists
    3c415431ffe3: Already exists
    47eb08f01e22: Already exists
    bb35d33eae84: Already exists
    f6e2c0f91fd9: Already exists
    38b3af3b1080: Already exists
    fa61be08855e: Already exists
    987bb75b0817: Already exists
    eef675aada05: Already exists
    38d9d717e243: Already exists
    ee86a4d62ca2: Already exists
    08be2fa1c4f0: Already exists
    —> b00e0fd9fb82
    Step 2/11 : RUN apt-get update && apt-get install -yq automake libtool git build-essential python
    —> Running in 2287816093df
    Get:1 jessie/updates InRelease [63.1 kB]
    Get:2 jessie InRelease [14.9 kB]
    Get:3 jessie InRelease [22.9 kB]
    Ign jessie InRelease
    Get:4 jessie-updates InRelease [145 kB]
    Get:5 jessie Release.gpg [2373 B]
    Get:6 jessie Release [148 kB]
    Get:7 jessie/updates/main armhf Packages [532 kB]
    Get:8 jessie/main armhf Packages [13.3 MB]
    Get:9 jessie/main armhf Packages [170 kB]
    rdt push failed. Error: The command ‘/bin/sh -c apt-get update && apt-get install -yq automake libtool git build-essential python’ returned a non-zero code: 137 Error: The command ‘/bin/sh -c apt-get update && apt-get install -yq automake libtool git build-essential python’ returned a non-zero code: 137
    at Stream. (/usr/local/lib/node_modules/resin-cli/node_modules/resin-sync/build/docker-utils.js:145:23)
    at emitOne (events.js:77:13)
    at Stream.emit (events.js:169:7)
    at drain (/usr/local/lib/node_modules/resin-cli/node_modules/through/index.js:36:16)
    at (/usr/local/lib/node_modules/resin-cli/node_modules/through/index.js:45:5)
    at Parser.parser.onToken (/usr/local/lib/node_modules/resin-cli/node_modules/resin-sync/node_modules/JSONStream/index.js:132:18)
    at Parser.proto.write (/usr/local/lib/node_modules/resin-cli/node_modules/resin-sync/node_modules/jsonparse/jsonparse.js:134:34)
    at Stream. (/usr/local/lib/node_modules/resin-cli/node_modules/resin-sync/node_modules/JSONStream/index.js:23:12)
    at (/usr/local/lib/node_modules/resin-cli/node_modules/through/index.js:26:11)
    at IncomingMessage.ondata (_stream_readable.js:528:20)
    at emitOne (events.js:77:13)
    at IncomingMessage.emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:146:16)
    at IncomingMessage.Readable.push (_stream_readable.js:110:10)
    at HTTPParser.parserOnBody (_http_common.js:109:22)
    at Socket.socketOnData (_http_client.js:305:20)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:146:16)
    at Socket.Readable.push (_stream_readable.js:110:10)
    at TCP.onread (net.js:523:20)


Hi, can you please make sure that you have used the Enable Local Mode action on the device, according to the docs?
Also, please confirm whether you are using a dev Resin OS image on your device.


These issues we’ve seen before, when the supervisor running on the device is not switched into Local Mode as mentioned, and then it will clear out user container and images it doesn’t know about - the cryptic “returned a non-zero code: 137” we’ve seen in such cases so far. In that case, the error would happen at different stages on each push.

Switching into Local Mode, the supervisor behaviour adapts, and won’t clean out containers it doesn’t know about.


The device was in local mode during error.