Note on Using Matter with Docker

• In general, we do not recommend using the Matter integration under Docker, as there are various requirements and restrictions here, some of which are also very technical and subtle.
• Synology/QNAP NAS have a kernel that is too old, so that Thread devices cannot run there at all, and LAN/Wi-Fi devices can only run in host/MacVLAN network mode.

If Matter is to be used under Docker, one of the two requirements must be met:

• Docker runs in MacVLAN network mode, so that the container has its own IP address in the network.
• Docker runs in host network mode. The host must not have Avahi installed. Otherwise there will be server collision error messages and the mDNS network resolution will not be reliable because two Avahi stacks are running in parallel.

Matter still does not work reliably with the following restrictions:

• Docker in bridge network mode does not work at all, as mDNS is not available as a result.
• Docker runs correctly in host network mode, but Avahi also runs on the host. As a result, Avahi runs twice. This is particularly the case with Synology/QNAP NAS. This will interfere with finding the devices via mDNS and devices will be sporadically unreachable/unreliable.
• If the kernel is too old, router announcements are not supported. This is particularly the case with Synology/QNAP NAS. In this case, Matter integration only works for LAN/WLAN devices and for Thread devices only if an IPv6 DHCP server is available that correctly assigns all addresses/routes to all devices/thread border routers.
• Incorrect or unset Sysctl settings. The configurator also points this out accordingly. In particular, this configures the router announcements so that Thread devices function reliably.