Improve this doc

Dockerfile Guide offers you the flexibility to deploy Docker containers to devices. This enables you to define your own environment and use whatever tools you need.

Images and Containers

To understand how this works we need to understand a bit about how Docker works and what images and containers are in this context. Basically an image is a read-only template or blueprint and the container is a running system built from an image. (see Docker's introduction for more details on this.)


To create a container from an image we use a Dockerfile - this is similar to a Makefile in that it contains a recipe or set of instructions to build our container.

The syntax of Dockerfiles is fairly simple - at core there are 2 valid entries in a Dockerfile - comments, prepended with # as in script files, and instructions of the format INSTRUCTION arguments.

Typically you will only need to use 4 instructions - FROM, RUN and ADD or COPY:-

  • FROM has to be the first instruction in any valid Dockerfile and defines the base image to use as the basis for the container you're building.

  • RUN simply executes commands in the container - this can be of the format of a single line to execute, e.g. RUN apt-get -y update which will be run via /bin/sh -c, or [ "executable", "param1", "param2", ... ] which is executed directly.

  • ADD copies files from the current directory into the container, e.g. ADD <src> <dest>. Note that if <dest> doesn't exist, it will be created for you, e.g. if you specify a folder. It also allows the to be a url, and if the is a recognised compression format, it will unpack it for you.

  • COPY is very similar to ADD, but without the compression and url functionality. According to docker best practise you should always use COPY unless the auto-extraction capability of ADD is needed.

  • CMD this command provides defaults for an executing container. This command will be run when the container starts up on your device, where as RUN commands will be executed on our build servers. In a application, this is typically used to execute a start script or entrypoint for the users application. CMD should always be the last command in your Dockerfile. The only processes that will be running inside the container is the CMD command, and all processes that it spawns.

For details on other instructions, consult the official Dockerfile documentation.

Using Dockerfiles with

To use a Dockerfile to deploy to simply place it at the root of your repository. When you push your code to it will automatically recognise it and use that to deploy code to your device.

You can also include a .dockerignore file with your project if you wish the builder to ignore certain files.

NOTE: You don't need to worry about ignoring .git as the builders already do this by default. Base Images

Raspberry Pi

We provide a base Raspbian Raspberry Pi image especially configured to run on at resin/rpi-raspbian:wheezy.

To use this image prefix your Dockerfiles with:-

FROM resin/rpi-raspbian:wheezy-2015-01-15

You will note that this image has a build date appended to it, we try to keep our builds as up-to-date as possible. To use the most up-to-date version or a previous version, check out the registry over here.

Example Dockerfile

Let's take a look at an example Dockerfile. This comes from the Hello Python project and executes a simple Hello World Python project:-

FROM resin/rpi-raspbian:wheezy-2015-01-15

# Install Python.
RUN apt-get update && apt-get install -y python

COPY . /app

CMD ["python", "/app/"]


Let's take a look at what's going on here, line-by-line:-

FROM resin/rpi-raspbian:wheezy-2015-01-15

Here we use the Raspberry Pi Raspbian image as our base Docker image.

# Install Python.
RUN apt-get update && apt-get install -y python

Next we update Raspbian's packages and install Python (using the -y switch to prevent any prompts on the build server.)

NOTE: All the commands in Docker RUN are executed on our build servers in a virtual qemu ARM device, so be careful not to run commands that require user intervention or try to access IO, because these will cause the build to hang and you won't get a lovely container pushed to your devices.

COPY . /app

Now we need to get the files in our repository. This command recursively copies all the files in the local directory (on the build server this will be the files in the repository) into a new directory in the container, /app. This could also be done using ADD, but COPY is recommended by the folks over at docker.

CMD ["python", "/app/"]

And finally we need to actually make our container do something great, so we do that by telling python to run our awesome script, which it can find at "/app/" because it was kindly placed there by the COPY command.

Dockerfiles for Other Programming Languages

There are a number of example Dockerfiles available for different languages listed on the projects page.