That’s the nice part: you decide it can be any path in the container or a path inside the host (don’t forget to make it available inside Portainer!)
My suggestion is to go for the simple “/config” option and to install the hass.io samba plugin later. If you do that you can always approach your config directory through a samba client.
Pick a place on the host OS that you want to store your configurations.
But, you guys aren’t installing HASSIO if you are running docker run. You are installing HOME ASSISTANT
hassio isn’t installed with the normal docker run commands. there are no addons with the normal home assistant docker image, which you have supplied the instructions for.
Given my confused attempts with Docker and the fact that I only need the NUC for Hass.io anyway, I thought it might be somewhat easier to just use the new NUC Hass.io image and do exactly what I did on the Raspberry Pi.
So I downloaded the NUC image, flashed it onto a USB stick, put the stick into a NUC with no preexisting partition. However, I get stuck at the very beginning when this menu shows up and none of the options seem to do anything.
Can anybody guide me towards the next steps?
On the Raspberry Pi, this worked without a problem, but the NUC seems to be a different animal.
Hey there. Check this thread. At the moment, you need to use DD or ZCat under Linux live to image the SSD on the NUC as there is no auto installer. It took me hours to work it out with the assistance of @BerryClam but once sorted, less than 5 minutes to get it working. Running sweet with 0.85.1 with 2% CPU.
gunzip -c /home/ubuntu/Downloads/hassos_intel-nuc-2.12.img.gz | sudo dd of=/dev/sda as he had downloaded the GZ using a live Ubuntu install instead. Both methods work.
The dd command images the SSD in full with the GZ file. I made a video while I did the process but at the moment it has no sound. Happy to share if that will help.
Thanks for this! How long did your installation take? Mine has been running for an hour now… Stuck at “wlp58s0: link is not ready”…
That seems to be the network connection (wired). In Ubuntu, the network connection works fine only after the restart after the above command, it hangs…