ioBroker under Docker
Docker puts ioBroker into a container: a self-contained package with everything it needs. The host system remains clean, and the container can be replaced without losing the configuration.
The image is maintained by buanet , not by the ioBroker project itself. It is the only one supported in the forum, and its official documentation is more comprehensive than this page – it covers everything about environment variables, time zone, permissions, and the intricacies of each adapter.
Docker is worthwhile if you already have a Docker host or a NAS. For your first ioBroker installation on your own device , installing it under Linux is the quicker route – one less layer to get in the way in case of errors.
Requirements
Before installation, check whether the system meets the requirements . The same values apply to the container as to a normal installation, plus whatever the host system itself requires.
The fastest way
docker run -p 8081:8081 --name iobroker \
-v iobrokerdata:/opt/iobroker \
buanet/iobroker:latest
After that, the surface is underhttp://<adresse-des-hosts>:8081 reachable.
Using docker compose
For continuous operation, a Compose file is the better choice because the settings are stored in one place and can be easily reviewed:
services:
iobroker:
image: buanet/iobroker:latest-v11
container_name: iobroker
restart: always
ports:
- "8081:8081"
volumes:
- iobrokerdata:/opt/iobroker
volumes:
iobrokerdata:
The three sticking points
The volume is the installation
Everything that makes ioBroker what it is – configuration, adapters, database, scripts – lies under/opt/iobroker Without a volume at this location, everything will be lost the next time the container is replaced.
A container is not a storage location. The container is replaced, the volume remains – that's the whole point. Anyone who forgets the volume will notice it during the first update.
A fixed day insteadlatest
latest It always points to the latest version, even across version jumps. Nextdocker pull This means a major version can be advanced without anyone having decided to do so. For a system that is intended to run, a tag with a major version or a fixed version is the right choice. The buanet documentation explicitly recommends this. The major version of the image in September 2026 was 11, and the tag is named accordingly.latest-v11 .
The network
In normal bridge mode, the container only sees the home network via forwarded ports. This is sufficient for most adapters. However, it's not sufficient where devices are searched for on the network – anything that uses broadcast or multicast: Philips Hue, Sonos, Chromecast, and the device search in the admin panel. Such adapters require host mode or a MACVLAN network.
Similarly, any connected hardware – a Zigbee stick, a CUL – must be explicitly passed through to the container.
Secure
The backup system is working as usual:iob backup The file is stored in the container, and the resulting file resides in the volume. Anyone who backs up the volume has everything. Additionally, the backitup adapter is worthwhile, as it can schedule backups and perform them remotely.