Help with network or docker setup when installing Hassio on Windows with VirtualBox

Installation
1

Hi All,

Been working on a problem with hassio that occurred last Wednesday. After a reboot of hassio virtual machine in VirtualBox my homeassistant installation didn’t come online (as in I couldn’t reach it via web-interface). Tried a proper shutdown and reboot a couple of times, but it didn’t help.

The first thing to do? Read the logs of course. But the only thing it said, was that it took longer than x second to set up this and that.

The second step to do? To the forum. Browsing the forum gave me the idea that it could have something to do with the homeassistant container not being able to reach the other containers.

So via VirtualBox UI I logged into the console of homeassistant. The UI was constantly bombarded with messages that port x entered blocking state, port x entered forwarding state, eth0 renamed from vethxxxxx etc. Searching the forum and googling resulted in more people having the same problem. For some people, it was fixed because they had a wrong configuration or they reverted a fresh update because of a bug. So tried all that with no luck.

Finally did a completely fresh install of hassio, without any luck, the same problem. And today I even fired up an old backup virtual machine which used to work, with the same result. No webinterface and no control over my devices.

I thought maybe it’s the network card so I switched from lan to wifi in virtualbox setup, again without any luck.

Since none of the hassio instances work I’m assuming something has changed in my host system (windows 10), the networksettings or virtualbox. But I have no clue how to validate or better fix it.

I’m hoping anyone has an idea where I can begin? I don’t want to reinstall my whole server, without first knowing if that’s causing the problem

2

I’ve added loglines from Host of what I think might be a hint towards the issue. But again I’ve no clue where to start debugging this

[   23.588998] audit: type=1400 audit(1589201651.082:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor" pid=2547 comm="apparmor_parser"
[   23.728368] audit: type=1400 audit(1589201651.082:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor///usr/bin/gdbus" pid=2547 comm="apparmor_parser"
[   23.728389] audit: type=1400 audit(1589201651.082:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor///usr/bin/git" pid=2547 comm="apparmor_parser"
[   23.728406] audit: type=1400 audit(1589201651.082:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor///usr/bin/socat" pid=2547 comm="apparmor_parser"
[   23.728490] audit: type=1300 audit(1589201651.082:2): arch=c000003e syscall=1 success=yes exit=71188 a0=6 a1=7f06c4c1e010 a2=11614 a3=fc items=0 ppid=2546 pid=2547 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="apparmor_parser" exe="/usr/sbin/apparmor_parser" subj==unconfined key=(null)
[   23.728662] audit: type=1327 audit(1589201651.082:2): proctitle=61707061726D6F725F706172736572002D72002D57002D4C002F6D6E742F646174612F73757065727669736F722F61707061726D6F722F6361636865002F6D6E742F646174612F73757065727669736F722F61707061726D6F722F68617373696F2D73757065727669736F72
[   24.386337] IPv6: ADDRCONF(NETDEV_UP): enp0s3: link is not ready
[   24.451933] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[   24.467384] IPv6: ADDRCONF(NETDEV_UP): enp0s3: link is not ready
[   24.533135] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready
[   28.993898] audit: type=1400 audit(1589201656.500:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=2592 comm="apparmor_parser"
[   29.069411] audit: type=1300 audit(1589201656.500:3): arch=c000003e syscall=1 success=yes exit=7945 a0=4 a1=201c570 a2=1f09 a3=fc items=0 ppid=2591 pid=2592 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="apparmor_parser" exe="/usr/sbin/apparmor_parser" subj==unconfined key=(null)
[   29.187924] audit: type=1327 audit(1589201656.500:3): proctitle=61707061726D6F725F706172736572002D4B72002F6D6E742F646174612F646F636B65722F746D702F646F636B65722D64656661756C74363435333433373130
[   32.055617] audit: type=1325 audit(1589201659.562:4): table=nat family=2 entries=5
[   32.092760] audit: type=1300 audit(1589201659.562:4): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=260ea60 items=0 ppid=2561 pid=2620 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-legacy-multi" subj==unconfined key=(null)
[   32.231625] audit: type=1327 audit(1589201659.562:4): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4E00444F434B4552
[   32.318036] audit: type=1325 audit(1589201659.599:5): table=filter family=2 entries=4
[   32.383857] audit: type=1300 audit(1589201659.599:5): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=1a55940 items=0 ppid=2561 pid=2622 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-legacy-multi" subj==unconfined key=(null)
[   32.523998] audit: type=1327 audit(1589201659.599:5): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D740066696C746572002D4E00444F434B4552
[   32.524020] audit: type=1325 audit(1589201659.599:6): table=filter family=2 entries=6
[   32.653695] Initializing XFRM netlink socket
[   32.977749] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
[   33.295470] IPv6: ADDRCONF(NETDEV_UP): hassio: link is not ready
[   35.646192] kauditd_printk_skb: 122 callbacks suppressed
[   35.646197] audit: type=1325 audit(1589201663.152:47): table=nat family=2 entries=23
[   35.722742] audit: type=1300 audit(1589201663.152:47): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=998620 items=0 ppid=2561 pid=2795 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-legacy-multi" subj==unconfined key=(null)
[   35.855681] audit: type=1327 audit(1589201663.152:47): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4400444F434B4552002D7000746370002D6400302F30002D2D64706F72740038383834002D6A00444E4154002D2D746F2D64657374696E6174696F6E003137322E33302E33332E313A383838340000002D690068617373696F
[   35.986396] audit: type=1325 audit(1589201663.241:48): table=filter family=2 entries=30
[   35.986555] audit: type=1300 audit(1589201663.241:48): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=1a5cb30 items=0 ppid=2561 pid=2797 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-legacy-multi" subj==unconfined key=(null)
[   35.986640] audit: type=1327 audit(1589201663.241:48): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D740066696C746572002D4400444F434B45520000002D690068617373696F002D6F0068617373696F002D7000746370002D64003137322E33302E33332E31002D2D64706F72740038383834002D6A00414343455054
3

Do you have other VM’s with networking problems?
Maybe try a new VM with a Linux Live CD image for testing.
VirtualBox up to date?

4

@VDRainer I do have a networkconnection within the virtual machine host, I can ping websites for example. I haven’t tried another VM with docker within the VM. I don’t have an idea of another project that has that.

5

I assume VBox has network issues, If you google ‘Windows 10 virtualbox bridged network issues’, it looks like you’re not alone.
Sorry, i’m using VBox on Ubuntu host, so i can’t look how settings should be.
Good luck! :+1:

1 Like
6

I didn’t have a chance to look into this yet, but I’m gonna try this route. Thanks

7

I just tried this, hassos on virtualbox, it works on my desktop, but I can’t get it to work on my laptop which is where I actually want to run it. It looks like it starts up OK, but I can’t get to the UI, I can’t even find the disk location to check the logs, where is the virtual disk?

8

If you run it in virtualbox, you can login to the shell (user: root, pass:[empty]). The prompt is “ha>”, there you can type ‘help’ to see your options. Use this to access the logs

9

Thankyou, I’ve got it working by setting a static IP using nmcli. But now I can’t get my Bluetooth dongle working, I’m guessing there no driver :thinking:

10

in the setting of virtualbox select usb3 and add a filter for the device you want to pass through

11

I tried that, but it failed to start.

12

Interesting, I don’t know how to help with that

13

I downloaded and installed VMWare workstation PRO and ran a clean install in with VMWare . Same problem. So I think it’s something within windows 10 or the hardware. But in regards to the hardware I also tried the WiFI adapter. I’m clueless

14

This is what is shows in VMware

image
image1920×1050 146 KB

15

I’m having the same issue VirtualBox on windows 10. I’ve tried a fresh set-up with a different ip address with no luck. I’m beginning to think VirtualBox on Windows 10 is not a good iidea as many posters seem to think it’s just a bad install.

16

Anyone find a fix for this? I’ve got it installed on MacOS with the same issues. There are so many messages scrolling though I cannot use the command line with HA.

17

did you solve the problem? i have exactly the same

18

Nope! Had to do a full reinstall on my trustworthy RPi

19

Heavens. Same thing happed to me as well. Everything was fine and dandy for months, until one afternoon, the machine stops… err the virtual machine that is. Also likely going to revert to my old RassPi until I have a minute to set up an ubuntu server to run HA with… If anyone magically comes up with a solution for this in the next few days… or ever… but especially in the next few days, I would love to know!

20

Good morning, Very new to HomeAssitant. Trying to do an installation on a windows a windows 10 I5 8Gb ram using Virtual box 6.1.16r1040961. I have dl several images vdi , vhd, ova, etc. I have statically assigned the ip tried dhcp etc. I get an error right after core dns updates from11 to 12.Not really sure to go with this I have tried wireless wired its a bridged connection running promiscus mode . DNS recursion works across all devices I have a netgear nighthawk 6700v2 router using charter for internet.

21-01-16 13:30:33 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-01-16 13:30:33 INFO (MainThread) [supervisor.plugins] dns does not have the latest version 2020.12.0, updating
21-01-16 13:30:33 INFO (SyncWorker_1) [supervisor.docker.interface] Updating image homeassistant/amd64-hassio-dns:2020.11.0 to homeassistant/amd64-hassio-dns:2020.12.0
21-01-16 13:30:33 INFO (SyncWorker_1) [supervisor.docker.interface] Downloading docker image homeassistant/amd64-hassio-dns with tag 2020.12.0.
21-01-16 13:30:48 ERROR (SyncWorker_1) [supervisor.docker.interface] Can’t install homeassistant/amd64-hassio-dns:2020.12.0 -> 500 Server Error for http+docker://localhost/v1.40/images/create?tag=2020.12.0&fromImage=homeassistant%2Famd64-hassio-dns: Internal Server Error (“Get “https://registry-1.docker.io/v2/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)”).
21-01-16 13:30:48 ERROR (MainThread) [supervisor.plugins.dns] CoreDNS update failed
21-01-16 13:30:48 ERROR (MainThread) [supervisor.plugins] Can’t update dns to 2020.12.0, the Supervisor healthy could be compromised!
21-01-16 13:30:48 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 0 Home Assistant secrets.

Thank you

Its resolved for some reason after dns 12 loaded it couldn’t reach the servers. My fix was to plug in the virtual box host directly into the cable modem and bypass the router completely. Strange because as a test I put the host into a dmz but its a double nat meaning the cable modem has a 192.168.0.1 network that goes to the wan and the 192.168.0.1 has my 192.168.1.1 hanging off that 0.1. Not sure if that helps anyone trying to do tge installation.