Home Assistant Supervised- newbie needs help

Installation
1

I’m trying to migrate my HA instance from a venv to docker. I’ve successfully installed the latest version and have HA running via docker. I’ve also installed portainer so I can manage the various HA containers. But here’s where I’m stuck. I want to shut down my new HA instance and copy over the configuration files from my existing installation. But if I shut down the new HA instance, I no longer have access to the command line console (via Portlandia). So how do I copy over the files from my old instance to the new one?

Thanks

Stan

2

Topic title is misleading.

Hass.io is now simply known as Home Assistant. Even when it was known as Hass.io, there was no specific “docker installation” (hass.io is/was already based on docker).

If the flavor of Home Assistant you attempting to install does not have Supervisor and add-ons, then that’s now called Home Assistant Core.

Home Assistant Core can be installed as python virtual environment (venv) or as a docker container. I believe that’s what your topic is requesting:

Home Assistant Core via docker - newbie needs help

Regarding your question, have you considered using Samba to share/copy the configuration files? (That’s what I’ve used in the past.)

3

Updated the title to more accurately reflect my environment.

I’ve successfully installed Home Assistant Supervised on the same laptop that I run my current HA instance via venv. But I’m a docker newbie so I’m not sure how to access the configuration files if the homeassistant container is not running. Can someone explain exactly how to access the files within the container so I can copy over my old configuration into my new instance?

Thanks

4

The configuration files are located in /usr/share/hassio and are owned by root.

In other words, the config files are not “within the container”.

5

Awesome! I’m assuming this is documented somewhere but I certainly missed it. If you could point me to where this is documented that would be great.

Thanks
Stan

6

I found it within the installer shell-script.