Move installation to another Docker host

milkywayfarer · March 19, 2023, 5:36pm

I recently discovered that my installation of Home Assistant Supervised is not healthy and is unsupported. This is because, for whatever reason you can imagine, Home Assistant does not like it when you have additional Docker containers besides its own.

The solution is simple:

Create a new Ubuntu Docker container
Set it up for a Supervised installation
Move every Home Assistant container to a newly created OS

And I’m stuck at the third step. Can someone who did this before explain how can I migrate every container including volumes, saving all the changes and configurations, to another Docker host? How to dynamically forward ports from that machine to my main machine when I need it? (afaik Docker does not support dynamic port forwarding from a running container)

mwav3 · March 19, 2023, 5:46pm

Supervised only works on Debian- these are the requirements. If you dont follow the requirements it will be flagged as “unhealthy” and wont update, or could stop working altogether

github.com

home-assistant/architecture/blob/6c8b378e8b7a5329f69fa81bcfe284d85ab522b6/adr/0014-home-assistant-supervised.md

# 0014. Installation method: Home Assistant Supervised

Date: 2020-06-03

## Status

Accepted

## Context

Define a supported installation method as per [ADR-0012](https://github.com/home-assistant/architecture/blob/master/adr/0012-define-supported-installation-method.md).

## Decision

This installation method provides the full Home Assistant experience on a regular operating system. This means, all components from the Home Assistant method are used, except for the Home Assistant Operating System. This system will run the Home Assistant Supervisor. The Supervisor is not just an application, it is a full appliance that manages the whole system. It will clean up, repair or reset settings to default if they no longer match expected values.

By not using the Home Assistant Operating System, the user is responsible for making sure that all required components are installed and maintained. Required components and their versions will change over time. Home Assistant Supervised is provided as-is as a foundation for community supported do-it-yourself solutions. We only accept bug reports for issues that have been reproduced on a freshly installed, fully updated Debian with no additional packages.

This method is considered advanced and should only be used if one is an expert in managing a Linux operating system, Docker and networking.

This file has been truncated. show original

If you install a supported supervised version on Debian you move the installation by taking a backup on the old machine and restoring it on a new one.

milkywayfarer · March 19, 2023, 5:52pm

Will the backup actually contain all the ESPHome and Z2MQTT configuration, MariaDB tables and Nginx SSL certs?

mwav3 · March 19, 2023, 5:55pm

A full backup on supervised includes the addon data as well

milkywayfarer · March 19, 2023, 6:43pm

(only manually installed or created add-ons, not those installed from the store)

I have installed all of my plugins from the store, and they currently contain data about network routing and Zigbee devices of my smart home. Does this mean I need to take an extra step backing up everything manually?

mwav3 · March 19, 2023, 7:38pm

Unless you changed the storage settings on your addons you installed from the store, they default to storing all the data in the same directory as your homeassistant config directory. If you explore that directory, all the files from your addons should be in there, and the documentation notes this directory is part of the backup.

Specifically for zigbee2mqtt, the default path for backup data is config/zigbee2mqtt . You can double check your zigbee2mqtt config to see if this is the directory for your install.

What might complicate or make your backup fail is the “unhealthy” state of the supervisor. Did you take a full backup ever before it was “unhealthy”?