Self-host Home Assistant with Docker Compose

Plateforme domotique pour contrôler et surveiller votre maison connectée localement.

This is still a work in progress.

The generated compose file and instructions may not be complete or correct for every app yet. Please report any issues you encounter to contact@bitflake.com.

The steps below take a few minutes end to end.

Docker compose setup and file
save the generated compose and env files.
Start Home Assistant with Docker Compose
bring the stack up and check it's healthy.

Requirements

You'll need these installed on the machine you're deploying to:

Docker

Packages Home Assistant and everything it depends on into an isolated container, so it runs the same way on your machine as it does everywhere else.

Install guide

Docker Compose

Reads docker-compose.ymland starts everything in it together. Ships with Docker Desktop. On Linux servers it's usually a separate install.

Install guide

1. Docker compose setup and file

Create a folder for Home Assistant and save the file below into it as docker-compose.yml. It describes every container the stack needs — Home Assistantitself and any supporting services, such as its database — along with the ports, volumes and environment variables each one uses. You'll also need an empty .env file in the same folder; Docker Compose reads it automatically and uses it to fill in the ${VARIABLE}references you'll see in the file below.

docker-compose.yml

version: "3.9"
services:
  home-assistant:
    image: homeassistant/home-assistant:latest
    restart: unless-stopped
    ports:
      - 8123:8123
    volumes:
      - config:/config
      - run:/run
    configs:
      - source: home-assistant-bflk-http-config.json
        target: /config/bflk-http-config.json
    entrypoint:
      - /bin/sh
      - -c
      - |
        mkdir -p /config/.storage
        [ -e /config/.storage/http ] || cat /config/bflk-http-config.json > /config/.storage/http
        exec /init
volumes:
  config: null
  run: null
configs:
  home-assistant-bflk-http-config.json:
    content: |
      {
        "version": 2,
        "minor_version": 2,
        "key": "http",
        "data": {
          "stable": {
            "server_port": 8123,
            "use_x_forwarded_for": true,
            "trusted_proxies": ["10.244.0.0/16", "172.16.0.0/12"],
            "ssl_profile": "modern",
            "cors_allowed_origins": ["https://cast.home-assistant.io"],
            "use_x_frame_options": true,
            "ip_ban_enabled": true,
            "login_attempts_threshold": -1,
            "created_at": "2026-08-07T00:00:00+00:00",
            "error": null,
            "error_message": null
          },
          "pending": null,
          "yaml_migration_done": true
        }
      }

Volumes

Home Assistant stores its data in named Docker volumes, so it survives container restarts and updates:

config mounted at /config: Home Assistant's configuration and state: configuration.yaml, the database, the .storage registry, and installed integrations.
run mounted at /run: Runtime directory for s6-overlay's supervision tree and the sockets Home Assistant's services talk over. Recreated on every start, so nothing here needs to survive a restart.

2. Start Home Assistant with Docker Compose

From the folder with docker-compose.yml and .env, run:

Terminal

Start Home Assistant and all its supporting services in the background.

docker compose up -d

The -d flag runs the stack in the background so it keeps running after you close the terminal. Docker will pull the images the first time, which can take a minute or two.

To check on it afterwards: docker compose ps shows whether containers are healthy, and docker compose logs -f follows their logs if something looks wrong. Once it's running, open http://localhost:8123 in your browser.