I just installed HA on a Debian Raspi, and while I see a load of other containers running, I don’t see the core image homeassistant:
root@venus-ha:/home/pi/Downloads# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
cf2e97756f36 ghcr.io/home-assistant/armv7-hassio-multicast:2022.02.0 "/init" 6 minutes ago Up 6 minutes hassio_multicast
218919deb355 ghcr.io/home-assistant/armv7-hassio-audio:2021.07.0 "/init" 6 minutes ago Up 6 minutes hassio_audio
e46f15d15387 ghcr.io/home-assistant/armv7-hassio-dns:2021.06.0 "/init" 6 minutes ago Up 6 minutes hassio_dns
c2ededc1a73c ghcr.io/home-assistant/armv7-hassio-cli:2021.12.0 "/init /bin/bash -c …" 6 minutes ago Up 6 minutes hassio_cli
1ba16444330b ghcr.io/home-assistant/armv7-hassio-observer:2021.10.0 "/init" 2 hours ago Up 7 minutes 0.0.0.0:4357->80/tcp, :::4357->80/tcp hassio_observer
d6fe5fbf69aa ghcr.io/home-assistant/armv7-hassio-supervisor "/init" 2 hours ago Up 7 minutes hassio_supervisor
root@venus-ha:/home/pi/Downloads#
I’ve ran the .deb install several times. What happened to homeassistant?
The output from the install looks “mostly” fine:
root@venus-ha:/home/pi/Downloads# dpkg -i homeassistant-supervised.deb
(Reading database ... 187762 files and directories currently installed.)
Preparing to unpack homeassistant-supervised.deb ...
[warn]
[warn] If you want more control over your own system, run
[warn] Home Assistant as a VM or run Home Assistant Core
[warn] via a Docker container.
[warn]
[warn] ModemManager service is enabled. This might cause issue when using serial devices.
Leaving 'diversion of /etc/NetworkManager/NetworkManager.conf to /etc/NetworkManager/NetworkManager.conf.real by homeassistant-supervised'
Leaving 'diversion of /etc/NetworkManager/system-connections/default to /etc/NetworkManager/system-connections/default.real by homeassistant-supervised'
Leaving 'diversion of /etc/docker/daemon.json to /etc/docker/daemon.json.real by homeassistant-supervised'
Leaving 'diversion of /etc/network/interfaces to /etc/network/interfaces.real by homeassistant-supervised'
Unpacking homeassistant-supervised (1.1.1) over (1.1.1) ...
Setting up homeassistant-supervised (1.1.1) ...
[info] Restarting NetworkManager
[info] Restarting docker service
PING version.home-assistant.io (104.26.5.238) 56(84) bytes of data.
64 bytes from 104.26.5.238 (104.26.5.238): icmp_seq=1 ttl=57 time=27.6 ms
--- version.home-assistant.io ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 27.646/27.646/27.646/0.000 ms
Device "eth0
eth0
eth0" does not exist.
[info] Install supervisor Docker container
[info] Install supervisor startup scripts
[info] Install AppArmor scripts
[info] Start Home Assistant Supervised
[info] Installing the 'ha' cli
[info] Switching to cgroup v1
[info] Within a few minutes you will be able to reach Home Assistant at:
[info] http://homeassistant.local:8123 or using the IP address of your
[info] machine: http://:8123
[warn] A reboot is required to apply changes to grub.
root@venus-ha:/home/pi/Downloads#
The eth0 error is strange, because it’s there:
root@venus-ha:/home/pi/Downloads# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.115 netmask 255.255.255.0 broadcast 192.168.1.255
ether b8:27:eb:df:1a:e1 txqueuelen 1000 (Ethernet)
RX packets 470618 bytes 650372750 (620.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 106976 bytes 9131321 (8.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Anybody know what happened? This is a freshly upgraded from Debian 9 => Debian 11 on Raspi.
1 post - 1 participant