Use the Docker CLI to pull this image
New major image versions (e.g. v4, v5, v6) always come with a new major version of node! This might lead to problems when you update your ioBroker container by simply recreating it from the new major version image! To avoid having trouble with recompiling adapters, it is recommended to upgrade your container manually with backup and restore procedure. For more details please see the maintenance part of the new ioBroker Docker image docs.
It is highly recommended not to use the
latest tag for production, especially when using any kind of automated update procedure like watchtower. Please use the
latest-vX tag instead.
For taking a first look at iobroker on docker it would be enough to simply run the following basic docker run command:
docker run -p 8081:8081 --name iobroker -h iobroker buanet/iobroker
When using docker-compose define the iobroker service like this:
version: '2' services: iobroker: container_name: iobroker image: buanet/iobroker hostname: iobroker restart: always ports: - "8081:8081"
To make your ioBroker configuration persistent it is recommended to mount a volume or path to
On command-line add
On docker-compose add
volumes: - iobrokerdata:/opt/iobroker
You could use environment variables to auto configure your ioBroker container on startup.
IOB_ADMINPORT(optional, default: 8081) Sets ioBroker adminport on startup
IOB_MULTIHOST(optional) Sets ioBroker "master" or "slave" for multihost support (needs additional config for objectsdb and statesdb!)
IOB_OBJECTSDB_HOST(optional, default: 127.0.0.1) Sets host for ioBroker objects db
IOB_OBJECTSDB_PORT(optional, default: 9001) Sets port for ioBroker objects db
IOB_OBJECTSDB_TYPE(optional, default: jsonl) Sets type of ioBroker objects db, could be "jsonl", "file" (deprecated) or "redis" (not officially supported).
IOB_STATESDB_HOST(optional, default: 127.0.0.1) Sets host for ioBroker states db
IOB_STATESDB_PORT(optional, default: 9000) Sets port for ioBroker states db
IOB_STATESDB_TYPE(optional, default: jsonl) Sets type of ioBroker states db, could be "jsonl", "file" (deprecated) or "redis"
AVAHI(optional, default: false) Installs and activates avahi-daemon for supporting yahka-adapter, can be "true" or "false"
ZWAVE(optional, default: false) Installs openzwave to support zwave-adapter, can be "true" or "false"
LANG(optional, default: de_DE.UTF‑8) The following locales are pre-generated: de_DE.UTF-8, en_US.UTF-8
LANGUAGE(optional, default: de_DE:de) The following locales are pre-generated: de_DE:de, en_US:en
LC_ALL(optional, default: de_DE.UTF-8) The following locales are pre-generated: de_DE.UTF-8, en_US.UTF-8
PACKAGES(optional) Installs additional linux packages to your container, packages should be separated by whitespace like this: "package1 package2 package3".
SETGID(default: 1000) In some cases it might be useful to specify the gid of the containers iobroker user to match an existing group on the docker host
SETUID(default: 1000) In some cases it might be useful to specify the uid of the containers iobroker user to match an existing user on the docker host
TZ(optional, default: Europe/Berlin) Specifies the time zone
USBDEVICES(optional) Sets relevant permissions on mounted devices like "/dev/ttyACM0". For more than one device separate with ";".
The examples above are dealing with the Docker default bridge network. In general there are some reasons why it might be the better choice to use a user-defined bridge network.
Using a Docker bridge network works fine for taking a first look and with most of the ioBroker adapters (if you don't forget to redirect the ports your adapters use). But some ioBroker adapters are using techniques like Multicast or Broadcast for automatic detection of IoT devices In this case it may be useful to switch to host or MACVLAN network.
For more information about networking with Docker please refer to the official Docker docs.
If you like what you see please leave us stars and likes on our repos and join our growing community. See you soon. :)