search

home-assistant / supervised-installer

Installer for a generic Linux system
Apache License 2.0
1.72k stars 585 forks source link

Installation error #43

Closed ggraziotti closed 5 years ago

ggraziotti commented 5 years ago

With the command on raspberry3 with raspbian ontano the error:

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | bash -s -- -m raspberry3

I execute has root user

Error:

"No networkmanager support on host" Can someone help me ?

tanasegabriel commented 5 years ago

This was made mandatory in https://github.com/home-assistant/hassio-installer/pull/36, but I'm not sure why, a PR description would have been handy in here.

Either way, I rebuilt my Pi based swarm cluster and Raspbian Buster doesn't come with network-manager. I don't see any value in migrating to it just for running Hassio, so I downloaded the installer script and commented out line #23 (previously it didn't also mean exiting with a non-zero status code and again, I've no idea why it should do that now) and everything seems to be working for me so far.

Maybe I'm missing something obvious here when it comes to this hard dependency, maybe @pvizeli can shed some light.

frenck commented 5 years ago

You need to install the NetworkManager dependency, package: network-manager. For more information and details, check out our documentation: https://www.home-assistant.io/hassio/installation/#alternative-install-on-a-generic-linux-host

The Network Manager is communicating over D-Bus, allowing Hass.io to get network information (like the upstream DNS servers).

tanasegabriel commented 5 years ago

That makes sense @frenck. Question is - should this be mandatory? In my opinion, this should be mandatory if the whole system would not work because of it.

I've been running Hassio for a couple of years without network-manager and I just re-installed it yesterday while overriding this.

What's the actual side-effect of not using it, provided that you have static IPs and static DNS servers (I bet this is the case for most of the Hassio users). I'm OK with submitting a PR for adding an argument used to skip this check if you accept this approach.

L.E.

I'm seeing this in the logs:

19-09-08 22:36:31 WARNING (MainThread) [hassio.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.

I found https://github.com/home-assistant/hassio/pull/1255, and the linked issues explains why this is needed (a bit obscure TBH)

While I do understand that my set up does not represent the norm, I for example run pihole outside of Hassio, so I already have an instance of dnsmasq running and the upstream DNS never changes. I find it a bit over the top to migrate to network-manager just for this. While the script can still exit if this is not present by default, a nice touch would be an option to skip this, such as --no-network-manager. One of the advantages of using the Docker installation is to have close to 0 dependencies on the host IMO, installing network-manager can be a breaking change for some hosts.

pvizeli commented 5 years ago

Feel free to contribute the dbus support for systemd-networkd (I think your system will use this, if you not relay on NM).

We start to support WLAN/Network setup over UI and I implement this for network-manager, but I do not block contributions for other backends with dbus support like systemd-networkd.

pvizeli commented 5 years ago

the offer is still open, but I revert the networkmanager