Running supervisor in the dev env

Deploy your local version to the devenv registry

If you haven't done so yet, login to the devenv registry:

docker login registry.resindev.io

Use username "resin" and the registry's default login details if you haven't changed them.

make ARCH=amd64 deploy

This will build the image if you haven't done it yet. A different registry can be specified with the DEPLOY_REGISTRY env var.

Set up config

Edit tools/dind/config.json to contain the values for a staging config.json.

This file can be obtained in several ways, for instance:

• Download an Intel Edison image from staging, open config.img with an archive tool like peazip
• Download a Raspberry Pi 2 image, flash it to an SD card, then mount partition 5 (resin-conf).

Start the supervisor instance

make ARCH=amd64 run-supervisor

This will setup a docker-in-docker instance with an image that runs the supervisor image.

By default it will pull from the devenv registry (registry.resindev.io).

A different registry can be specified with the DEPLOY_REGISTRY env var.

e.g.

make ARCH=amd64 DEPLOY_REGISTRY= run-supervisor

to pull the jenkins built images from the docker hub.

View the containers logs

logs supervisor -f

View the supervisor logs

enter supervisor
tail /var/log/supervisor-log/resin_supervisor_stdout.log -f

Stop the supervisor

make stop-supervisor

This will stop the container and remove it, also removing its volumes.