[haos-one] Run Home Assistant OS in Docker Container (for those migrating from depricated Supervised)

Installation Home Assistant OS
1

As you may know, the Supervised installation method has been deprecated.

So, I built haos-one : a single Docker container that runs Home Assistant OS with Add-ons.

intro-ezgif.com-speed

No dedicated hardware or VM needed.

For ex-Supervised users who want full-featured Home Assistant running next to other services.

Try it:

docker run -ti --privileged -p 8123:8123 \
-v ./data:/mnt/data \
qweritos/haos-one

Works on x86/ARM hosts, supports rootless containers

Feedback welcome.

Glad if you find it useful!

3 Likes
2

Hi everyone,

I wanted to share my challenges for anyone considering migrating their Supervised installation to the new haos-one Docker container, specifically if you are running on Linux (Ubuntu/Debian) and connected via Wi-Fi.

I spent the last few hours trying to get this working and hit a major roadblock that leaves you stuck between “crashing your network” or “breaking your devices.”

The Problem:

  1. Host Mode Crashes Network: The documentation recommends network_mode: host. On my Linux machine, doing this caused the container to hijack my host’s network interfaces. It literally renamed my virtual interfaces to eth0, killing my SSH connection and taking the host offline. I had to restart to recover.
  2. Bridge Mode Breaks Discovery: To stop the crashing, I switched to bridge mode. While Home Assistant starts and is accessible, discovery protocols fail. My Govee lights (Local API) and Matter/HomeKit devices stopped working because the container can’t send/receive the necessary broadcast packets through the Docker bridge.
  3. IPVLAN doesn’t work on Wi-Fi: Trying to give the container its own IP (IPVLAN) fails because Wi-Fi access points generally block multiple IPs on a single MAC address.

Summary:
If you are on Ethernet, you might be fine (or maybe Macvlan works for you). But if you are on Wi-Fi, be very careful. haos-one seems to try to manage the underlying network hardware in a way that conflicts with the host OS, and there is currently no easy workaround to get local device control (Govee/Matter) working without risking your host connection.

Just a heads-up before you start your migration!

3

Check your router. Some routers apply restrictions routing between WiFi and Ethernet.

4

Excellente initiative pour ceux qui veulent garder HA OS sans se prendre la tête avec Proxmox ou une VM dédiée ! J’ai justement un serveur Docker avec plusieurs services qui tournent et je me demandais comment gérer ça proprement. Question bête : la migration depuis une install Supervised existante est smooth ou faut tout reconfigurer de zéro ? :thinking: