does this method work for you?
have you made changes to the ssh command?
I can’r install containers such way.
Hi there all,
I just installed the Hass OS in my Qnap 882 using the OVA image
It was installed in 10 secs 
But first os all… now my Hass OS with about 6-8 Add-on have a restart in just 11 sec
Grate grate story !!! so THANKS A LOT TO ALL DEVELOPERS !!!.
So i have installed Hass OS in a 6 GB hard disk image and after installation,
I remember it was about at 20% of HD
Then I installed some apps:
Node-Red, Samba, VSC, MQTT, ADB - Android Debug Bridge, Log Viewer and TasmoAdmin.
Then supervisor give me an error… something about I have no more spaces on the HD
…I was at about 85-87% od HD.
So here is the problem… I power off the Hass OS VM and I resized the HD from 6 to 10 GB.
And at this point the OS is not started anymore… I take this error:
I restart the Qnap, but nothing…
And I don’t know where to see some other details.
And because I was not happy, I remake all this thinks from begining… using same steps.
HD of 6 GB at start, installed Hass OS VM, installed some apps
and then sized HD again from 6 to 10 GB.
… same error 
Is there anybody can help me to understand why I can’t resize the Hass OS hard disk please ?
Thanks a lot all.
…and again congratulations !!!
How do you resize you partition?
I once done it and it work easy and great
I just stop the VM, the I go in setting > memory and there I put 10 where now it’s 6
Then I start the VM and boom
Is there something else that I must do please ?
Thanks again
Denis
Actually i did same thing…
Maybe just create new VM with 10 gb of disk space and use it?
I understand now… just take off the writeback and let none
and at this point it let you to resize the HD.
Don’t ask me why
Then after resize, just put back writeback
All ok now
Denis
Hope you dont mind me jumping on this thread to ask for some help but struggling to fix my setup. Ive has HASSIO running on VM on my qnap 251 since april without many issues until this morning. It wont boot up, sits there showing " Shell> " . When i reboot i get a brief glimpse of something saying "BdsDxe failed to load Boot0002. Now im sure i can create a new VM but ive lost my configuration which has taken me months to sort. I have a copy of the latest config.yaml but is there anyway i can either get it to reboot or find a way of retrieving files from the installation that wont boot that i can drop into a fresh install. Any help much appreciated
Hej,
also trying to get this working, can you share your improvements? as I get stuck on 4 containers now…
This is the setup I had once I upgraded to Ubuntu 20.4 I kept getting the message that I am running an “Unsupported Installation” Are you getting this message?
I am exploring the debian route, since debian seems to be the offical supported linux version that can run home assistant in supervised mode. Currently I am able to run debian 10, ubuntu 20.4. with hass os in supervised mode. I am finding that home assistant is not auto starting. Working on figuring that out.
Hello everyone! I have tried to install HA in Container Station, where I got the HA Core to work with my laptop inside my home network (behind NAT). Then I installed the OVA version in Virtualization Station to access Hassio/HA Supervisor edition. I setup Virtio for Network setting like you suggested. Everything installs just fine and I get to CLI and I can log in to HA. But I cannot connect to the GUI version in port 8123 with my laptop. Inside HA CLI, I give command “core info” and it says the IP is 172.30.32.1 but my QNAP is on 192.168.0.3 inside my home network. I also cannot see the IP (same problem as Bryan) under the Virtualization settings.
Edit: quick answer to myself. I tried to go to URL http://homeassistant.local:8123 and it worked! I used “tracert homeassistant.local” in my Windows CMD and found out the IP is 192.168.0.11:8123 for some reason. Awesome. Hope everything works now … 
(You might have known this already but) FWIW, one could probably also get the IP of your HA instance from your router, usually under DHCP section.
Hi
Has anyone created/installed HASSIO via the container station APi ?
http://qnap-dev.github.io/container-station-api/container.html#create-a-container
It seems straight forward-ish. I’m doing some testing at the moment with another Docker image, but I’m getting stuck on the network settings ?
I’ve put in this, so it uses ‘bridge’
"network": {
"mode": "bridge",
"join": true
},
But I’m getting the following error message
{
"error": {
"code": 400,
"message": "get network setting failed"
}
}
I create my dockers through portainer, als much easier to update them… but only HA in this case and not Hassio
The Container Station api looks promising, and if I could get it working (for my use case) it’ll be good to be able to spin up containers quickly, via the command line and keep everything in one place.
For those that are interested, I’ve posted a guide on how to create an HA Docker container via the QNAP (Container Station API)
Hi,
I am using the QNAP TS-431X2, newest firmware = 4.5.2.1566, its a armv7 32 bit machine.
I have adapted the command above:
docker run -d --name “hassio-supervisor” --restart always -v /var/run/docker.sock:/var/run/docker.sock -v /var/run/hassio-hc.sock:/var/run/hassio-hc.sock -v “/share/Container/Home Assistant/HASS/data”:/data -v “/share/Container/Home Assistant/HASS/log”:/var/log -e SUPERVISOR_SHARE="/share/Container/Home Assistant/HASS" -e SUPERVISOR_NAME=“hassio-supervisor” -e HOMEASSISTANT_REPOSITORY=homeassistant/qemuarm-homeassistant homeassistant/armhf-hassio-supervisor
No I am getting the following error:
[02:50:32] INFO: Starting local supervisor watchdog…
Fatal Python error: pyinit_main: can’t initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0x75af4390 (most recent call first):
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Any ideas for fixing?
Regards,
Gerhard
Hi,
first improvement:
I inserted the option “–privileged” and the container armhf-hassio-supervisor is running and creating futher containers, which are also being “up”:
armhf-hassio-dns:2021.01.0
armhf-hassio-cli:2021.02.1
armhf-hassio-observer:2020.10.1
armhf-hassio-multicast:3
But the armhf-hassio-audio:2021.02.1 is “exited” and is staying “exited”
and the qemuarm-homeassistant:2021.2.3 is on the status “created” based on the error message below:
Further ideas?
Regards,
Gerhard
Hi,
the issue with the armhf-hassio-audio:2021.02.1 is also based on the jemalloc issue.
Still trying to stop the container and fix the jemalloc issue with commenting out the the jemalloc library.
But there should be a possibility to install this library on the QNAP box, or keep it out of the Home Assistant images…
Regards,
Gerhard
Hi,
i also have started with HA in Ubuntu on VM (inofficial way). But with the new .OVA official Image for VM e.g. Qnap its for me the best Usability. I set up in the VM an automated Every-Day-Snapshot. And before i take the new Updates, i generate a VM-Snapshot. it takes less then minute.
And if something going wrong, i can step back in also less then a minute. in a very bad mistake i can jump from one snaphost to other, for searching a stable Version and going from this. But was not needed because the HA Devs do a great job. Thanks a lot on this point.
Very happy with my environment in the Virtualization Station. it saved me time hours for backing up and waiting for updates.
Thanks alot!