I have been using docker on my Synology 918+ (with usb Aeotec zwave stick & usb zigbee2mqtt stick) for a while. everything works flawlessly. Last week end I tried the HassIO (VMDK) image on synology Vitual Machine manager and it also seems to work fine. Now I am wondering which one to choose going forward.
In theory, running home assistant container directly on docker could have a resource advantage as it eliminates the HassOS layer (virtual machine). On the other hand, HassIO makes it easy for addons. but I already have separate docker containers and they all work fine.
Also on HassIO the upgrade process is straightforward and restarts will take significantly less time than docker (apparently).
are there any other significant advantages/dis-advantages?
If your Synology is not really stretched for resources, use whichever you find easier. If you are trying to conserve resources, try and stick to Docker as it is a lot less resource hungry than the Synology VM hypervisor.
I have a Synology and haven’t really played around with the VM platform, because I have really enjoyed using docker for it’s ability to destroy and recreate containers so easily. Makes HA upgrades and downgrades a breeze.
Docker hardly uses 2-5% of CPU and about 400mb ram (for HA, mqtt, zigbee2mqtt together)
the minimum for virtual machine is 1GB ram, But I gave it 2GB to be on safe side. Also the CPU usage is also significantly higher (depending on addons we use).
Clearly there is no significant advantage for using virtual machine at this point. Faster restarts seems to be the only thing in favor.
I like the idea of running HASSOS as a virtual machine in Synology’s Virtual Machine Manager. I have a DS918+ with 4gb RAM, did you import the HassIO image or the HASSOS image? I have the latest HASSOS .vmdk from https://github.com/home-assistant/hassos/releases but not sure how to import it properly. I have done alot of searching but can’t find exactly what I’m after. Any help would be awesome.
Hi cpuram,
I was able to create the image using the .vmdk file but it only took a few seconds to make it! Then I created a virtual machine using UEFI and it when I pressed ‘connect’ I was able to see the command line scrolling passed. But at no time could I see it on my local network or find an IP address for it. I thought it was finished so in the virtual machine I could press enter and it would come up with the Hassio login line. Not sure what to try next, I used the following settings…
2 CPU’s
2GB RAM
Videocard is VMVGA
No additional ISO’s
10gb Storage
Default VM Network
Boot From Virtual Disk
BIOS - UEFI
Keyboard - Default
Virtual USB Controller - disable
Permissions - All local users & Groups (In case it was a permission thing)
I have tried the latest 2.24 as well as an earlier 1.12 version. Even tried the NUC image version but still no luck. I must be missing something!
Any help would be great
Cheers,
Simon.
Have you guys find a solution? I’m also on Synology using the virtual machine manager. I get everything running except that I don’t get IP to connect (same Ip as the Synology server also doesn’t work). Also I’m unable to find a way to see the network to bridge as I do on Virtual box
Hey guys, i tried to do the process to setup a virtual machine on Synology VMM, i downloaded the hassos_ova-2.11.vmdk and uploaded the IMAGE, then started VM with parameters that you guys tell before like
2 CPU’s
2GB RAM
Videocard is VMVGA
No additional ISO’s
10gb Storage
Default VM Network
Boot From Virtual Disk
BIOS - UEFI
Keyboard - Default
Virtual USB Controller - disable