The Webcoast
Back to Home Assistant

Setting up Home Assistant

Home Assistant is the one app in this Library where the two tabs below are genuinely different installs, not the same steps run in two places. Docker gets the core automation engine; Proxmox gets the full Home Assistant OS with its Supervisor and Add-on store, which Docker alone can't offer.

How are you running this?

Docker works the same on any Linux box and it's what I run day to day. Proxmox earns its extra layer specifically when it buys something Docker alone doesn't: snapshot-and-rollback for the whole app environment, a hard isolation boundary from everything else on the host, or the app simply isn't a Docker app to begin with. If none of that applies here, a plain Linux server is simpler.

  1. 1

    Run the container

    This is the "Home Assistant Container" install: the core automation engine, with host networking so device discovery (mDNS, SSDP) works the same as it would running directly on the machine.

    services:
      homeassistant:
        image: ghcr.io/home-assistant/home-assistant:stable
        container_name: homeassistant
        restart: unless-stopped
        network_mode: host
        volumes:
          - ./config:/config
          - /etc/localtime:/etc/localtime:ro
  2. 2

    Finish the onboarding wizard

    Reachable at port 8123, the first visit walks through creating the admin account, setting the home's location, and an initial device scan.

  3. 3

    Know what this method doesn't include

    This is the trade-off worth knowing up front: the Container method doesn't include the Supervisor, which means no Add-on store (no one-click Mosquitto, no built-in backup UI, no built-in USB/Bluetooth proxy add-ons). Anything like that has to be run as its own separate container instead. If that store matters, the Proxmox tab is the way to get it.

Further reading