How to install Node Red on UNO Q using Docker

Node Red

Arduino® UNO™ Q 2GB

<html><body>If you like the “one tiny computer that becomes a real dashboard” vibe, Node-RED on UNO Q is exactly that. You will get a browser-based visual editor that runs on the Linux side of UNO Q, and it’s perfect for wiring APIs, dashboards, and device logic together without turning your project into a full-time software job. <figure><img src="https://projects.arduinocontent.cc/5c80870d-5365-4a52-aed1-3275fdfd10ab.png"/><figcaption></figcaption></figure> This tutorial shows the fastest path using Docker. What you need: You’ll need an Arduino UNO Q connected to internet, plus another computer on the same network to open the Node-RED editor in a browser. If you want to access it by name, your network should support mDNS/Bonjour (most home and office networks do). Connect to your UNO Q From your usual computer, open a terminal and SSH into the board: <pre>ssh arduino@&lt;IP Address or mdns name&gt; </pre> Once you’re in, it’s a good habit to update packages before you install anything new: <pre>sudo apt update </pre><pre>sudo apt full-upgrade -y </pre><pre> </pre>After it reboots, SSH in again. Install and run Node-RED using Docker This is the cleanest route because everything (Node.js + Node-RED + dependencies) lives in a container, and your flows persist in a Docker volume. Good news here! Docker is already installed on the UNO Q so you don't have to start from scratch! Now run Node-RED using the official image and the command you provided: <pre>docker run -it -p 1880:1880 -v myNodeREDdata:/data --name mynodered nodered/node-red </pre> That's it! At this point Node-RED is running, and port 1880 is exposed. Open the Node-RED editor On your usual computer, open: <pre>http://&lt;uno_q_ipaddress&gt;:1880 </pre>You should see the Node-RED flow editor in your browser. If the page doesn’t load, the two most common causes are that the hostname isn’t resolving (try the board’s IP address instead of mdns name) or that port 1880 is blocked by a firewall on the network. How to make Node-RED survive reboots (the Docker way) When you run Node-RED in Docker, “auto-start on boot” is typically done with Docker’s restart policy rather than systemctl. The simplest approach is to recreate the container with a restart policy, so it comes back automatically after a reboot: <pre>docker rm -f mynodered </pre><pre>docker run -d -p 1880:1880 -v myNodeREDdata:/data --name mynodered --restart unless-stopped nodered/node-red </pre> This keeps your /data in the same Docker volume, so your flows and settings remain. Once Node-RED is up, the “Arduino way” to make it shine is to treat it like your integration canvas: one side talks to the real world (sensors, serial, MQTT, Modbus, REST), and the other side becomes your dashboard, alerts, and cloud bridge. </body></html>

How to install Node Red on UNO Q using Docker

Install Node-RED on UNO Q with Docker in one command and you’ll get a full visual automation dashboard on the board in minutes—no dependency drama, just fast prototyping at the edge.