Need help with docker-iobroker?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

129 Stars 59 Forks MIT License 377 Commits 2 Opened issues


Official Docker Image for ioBroker

Services available


Need anything else?

Contributors list

Official Docker Image for ioBroker

Release Build Status
Image Size Docker Pulls Docker Stars
Source License Donate

This image is a ready to use Docker image for ioBroker IoT platform (

It was originally created for running on a Synology DiskStation 1515+ with DSM 6 and official Docker package installed, but should run on any other Linux based Docker host too.

After years of development it might be the best documented and maintained Docker image for running ioBroker IoT platform with Docker.

Since v4.0.0 the image is available for the following architectures: amd64, armv7hf, aarch64.

In v5.1.0 it became the official Docker Image for the ioBroker Project.

Important notice

In general a new major version (e.g. v2, v4, v5) of the image comes with a new, preinstalled major node version! If you are updating an existing installation to a new major version (e.g. from v4 to v5) you have to perform some additional steps inside ioBroker! For more details please see official ioBroker documentation: EN | DE.

You might avoid these procedure if you use my "Best practice" hint for "upgrading your ioBroker container".

In any case make a backup first!

Getting started

A detailed tutorial (German, based on v3.0.0) can be found here: Please notice that the old tutorial is outdated and does no longer work!

For discussion and support please visit ioBroker forum thread or use the comments section at the linked tutorial.

Please do not contact me directly for any support-reasons. Every support question should be answered in a public place so every user can benefit from it . Thanks in advance.

If you think you found a bug or simply want to request a new feature please open an issue on Github so we can talk about.

The following ways to get iobroker-container running are only examples. Maybe you have to change, add or replace parameters to configure ioBroker for fitting your needs.

Running from command line

For taking a first look at the iobroker docker container it would be enough to simply run the following basic docker run command:

docker run -p 8081:8081 --name iobroker -v iobrokerdata:/opt/iobroker buanet/iobroker:latest

Running with docker-compose

You can also run iobroker by using docker-compose. Here is an example:

version: '2'

services: iobroker: restart: always image: buanet/iobroker:latest container_name: iobroker hostname: iobroker ports: - "8081:8081" volumes: - iobrokerdata:/opt/iobroker

Special settings and features

The following will give a short overview.

Environment variables

To configure the ioBroker container on startup it is possible to set some environment variables. You do not have to declare every single variable when setting up your container. Variables you do not set will come up with their default value.

Important: In v4.2.0 the ENVs "ADMINPORT" and "REDIS" were renamed/ reorganized. For Details see the following table!

|ENV|Default|Description| |---|---|---| |AVAHI|false|Installs and activates avahi-daemon for supporting yahka-adapter, can be "true" or "false"| |IOBADMINPORT|8081|Sets ioBroker adminport on startup| |IOBMULTIHOST|[not set]|Sets ioBroker instance as "master" or "slave" for multihost support (needs additional config for objectsdb and statesdb!)| |IOBOBJECTSDBHOST||Sets host for ioBroker objects db| |IOBOBJECTSDBPORT|9001|Sets port for ioBroker objects db| |IOBOBJECTSDBTYPE|file|Sets type of ioBroker objects db, cloud be "file", "redis" or "couch"
(at the moment redis as objects db is not supported by ioBroker)| |IOBSTATESDBHOST||Sets host for ioBroker states db| |IOBSTATESDBPORT|9000|Sets port for ioBroker states db| |IOBSTATESDBTYPE|file|Sets type of ioBroker states db, could be "file" or "redis"| |LANG|deDE.UTF‑8|The following locales are pre-generated: deDE.UTF-8, enUS.UTF-8| |LANGUAGE|deDE:de|The following locales are pre-generated: deDE:de, enUS:en| |LCALL|deDE.UTF-8|The following locales are pre-generated: deDE.UTF-8, enUS.UTF-8| |PACKAGES|[not set]|Installs additional linux packages to your container, packages should be seperated by whitespace like this: "package1 package2 package3"| |SETGID|1000|For some reasons it might be useful to specify the gid of the containers iobroker user to match an existing group on the docker host| |SETUID|1000|For some reasons it might be useful to specify the uid of the containers iobroker user to match an existing user on the docker host| |TZ|Europe/Berlin|All valid Linux-timezones| |USBDEVICES|none|Sets relevant permissions on mounted devices like "/dev/ttyACM0", for more than one device separate with ";" like this: "/dev/ttyACM0;/dev/ttyACM1"| |ZWAVE|false|Will install openzwave to support zwave-adapter, can be "true" or "false"|

Mounting folder/ volume

It is possible to mount an empty folder to /opt/iobroker during first startup of the container. The startup script will check this folder and restore content if it is empty.

Since v4.1.0 it is also possible mount a folder filled up with an iobroker backup file created using

iobroker backup
command or backitup adapter. Please make sure the name of your backup file ends like this:

The startup script will then detect this backup and restore it during the start of the container. Please see container logs when starting the container for more details!

Note: It is absolutely recommended to use a mounted folder or persistent volume for /opt/iobroker folder!

You can also mount a folder containing an existing ioBroker-installation (e.g. when moving an existing installation to docker). But watch for the used node version. If the existing installation runs with another major version of node you have do perform additional steps. For more Details see the "Important notice" on top of this file.

Important: If the folder you mount to /opt/iobroker in your container is placed on a mounted device, partition or other storage, the mountpoint on your host should NOT have the "noexec" flag activated. Otherwise you may get problems executing ioBroker inside the container!

Mounting USB device

If you want to use a USB device within ioBroker inside your container don´t forget to mount the device on container startup and use the environment variable "USBDEVICES".

User defined startup scripts

It is possible to add some script code to container startup with the help of the userscripts feature. You can get this to work by mounting an additional folder to

into the container.

When you mount an empty folder the startup script will restore two example scripts in there. To activate the scripts you have to remove the

part of the name. The "" will execute only at the very first start of a new container, while the "" will execute on every container start.

Feel free to test it with my example code. Take a look at the log. In "Step 4 of 5: Applying special settings" you will see the messages generated by the example userscripts.


With the help of the ENV "IOB_MULTIHOST" and the ENVs for objects and states db connections (see ENVs table above) it is now possible to run a container as standalone, multihost master or multihost slave. This is more or less a feature for advanced users. Please make sure you know how ioBroker multihost is working and set the ENVs as with

ìobroker setup custom

There is no need for executing

iobroker multihost enable
iobroker multihost connect
inside the container. Just configure the mentioned ENVs. The startup script will do all the magic.

For general information about iobroker multihost feature please see official ioBroker documentation.


Since v5.1.0 the image contains a simple Docker healthcheck. At the moment it only checks if js-controller is running inside the container and reports "healthy" or "unhealthy" to the Docker daemon. Further development is planned.

The healthcheck is configured to 5 retries in an 15s interval with a timeout of 5s. So a container needs a minimum of one minute to get unhealthy.

Hint: As the Docker daemon itself gives no opportunity to automatically restart an unhealthy container you might want to setup some kind of "watchdog container" like this simple one:

Maintenance script (beta)

Within the implementation of the docker health check (above) some manual maintenance actions, like stopping ioBroker for upgrading js-controller, would cause the container to get "unhealthy" and may cause an external watchdog to automatically restart it.

In this case you can use the new maintenance command line tool inside the container. By simply typing

maintenance on
it will activate some kind of "maintenance mode" and automatically stop ioBroker while the container stays healthy.

After your maintenance is done just type

maintenance off
. Depending on the selected restart policy of your container, the command will stop (and automatically restart) it.

Best practices

Avoid using "latest" docker tag

To avoid conflicts when upgrading your container or getting in trouble when accidentally upgrading your container to a new major version I prefer using a version docker tag like "v4.2.0" instead of "latest" for creating your container.

With v5.1.0 an additional docker tag "latest-[major version]" is available. This gives you the possibility update your container automatically while always staying in the same major version.

Upgrading your container

If you want to upgrade your ioBroker container to a new major version (e.g. from v4 to v5) I would prefer to do that by creating a backup in ioBroker (by "iobroker backup" or backitup adapter) and restoring it to a completely new container. All you need is time an the following steps: * make a backup by command line ("iobroker backup") or backitup adapter * stop the old container * create a new and empty data folder or volume and place your backup file in it * create a new container as your old or as you need it and use the new data folder/ volume for the /opt/iobroker mount point * follow the log output of the container and be patient

After this steps the startup script inside the container will automatically detect and restore your backup to a new ioBroker instance. When iobroker is started after the restore it will install your adapters to the new ioBroker instance by itself. This might take some time but will give you the best and cleanest results...


Beta testing

If you want to get the newest features and changes feel free to use/ test the beta version of the Docker image. You can find the file for beta versions here. Please make sure to read the changelog before testing beta versions.

Subscribe to updates

If you want the newest updates about the image and my tutorials at you can simply subscribe to my new "news and updates" channel (only in German) on Telegram. You will find the channel here:

Support the project

The easiest way to support this project is to leave me some likes/ stars on Github and Docker hub!
If you want to give something back, feel free to take a look into the open issues or the ioBroker forum thread and helping me answering questions, fixing bugs or adding new features!
And if you want to buy me a beer instead, you can do this here:
Thank you!


Moved to


MIT License

Copyright (c) 2017 [André Germann]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.



Inspired by

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.