Local build or docker container?
Tuesday, July 14th, 2026 at 08:05pm
When I originally setup Zigbee2MQTT on a Pi I followed the recommended path for Linux, which was to install Node.JS, clone the Zigbee2MQTT repo and then start it up. That first startup would install dependencies and build the app.
Over time I was able to at least once use the provided upgrade script to upgrade to the latest version in-place, but it then got to a point where the upgrade would crash the Pi and fail. Due to the Pi I am using only has 512MB (some reserved for video which I don’t use) one recommendation was to set memory limits for the build, but that just caused the build to fail with an out of memory error.
So I didn’t upgrade.
I knew I needed to get the upgrades working so when I started considering upgrading the Pi I use for Kodi an additional benefit was that I could replace the Pi 3 A+ with a Pi 3 B+ that has double the memory. But then what would I use the current A+ for? It felt a bit of a waste to upgrade the hardware for just the build process, because otherwise the A+ is running Zigbee2MQTT fine.
I preparation for a potential new install of Zigbee2MQTT I went back and reviewed the install instructions, which is when I found that their recommendation is now to just use Docker. I am fine with using multiple docker containers on my linux box to run various services, but it still felt a bit wrong to have a computer for a single task running a full operating system which then runs docker for a single container…
But it works and I have now upgraded Zigbee2MQTT to the latest version without upgrading hardware.
Tagged with: home automation, zigbee




