Dear Community,
I have two instances of Home assistant - one running on my server at home (intel CPU) and one running on RPI 3B, both running Dietpi (modified debian) as base OS. Currently running the latest version (the last run of “docker-compose pull” was just a week ago).
Even though I configured both computers in (almost) exactly the same way, on the RPI hass in docker works perfectly, on the intel CPU it just exits after some time running. (edit: before exiting, it works perfectly, too - the only problem is, that it suddenly exits)
Few months ago, I installed the RPI following this guide:
With minor tweaks this install works flawlessly and brings me a lot of joy - even though I basically only use it to turn on the heating before we leave for our WE house.
When installing on the intel CPU, I changed the docker compose yaml file to pull the home assistant for amd64, however after running for some time (several hours to days), the docker silently stops working - as far as I can tell with graceful exit.
The docker-compose.yaml on the intel CPU contains:
version: '2.1'
services:
homeassistant:
container_name: homeassistant
image: homeassistant/home-assistant
network_mode: "host"
volumes:
- /home/hass/homeassistant:/config
- /etc/localtime:/etc/localtime:ro
restart: unless-stopped
mosquitto:
container_name: mosquitto
image: eclipse-mosquitto
user: "1000:1000"
ports:
- 1883:1883
- 9001:9001
volumes:
- /etc/localtime:/etc/localtime:ro
- /home/hass/mosquitto:/mosquitto/config:ro
- /home/hass/mosquitto:/mosquitto/data
restart: unless-stopped
HASS is started by systemd on startup
[Unit]
Description=Docker Compose Opt Service
Requires=docker.service
After=docker.service
[Service]
Type=oneshot
RemainAfterExit=yes
WorkingDirectory=/home/hass/
ExecStart=/usr/local/bin/docker-compose up -d
ExecStop=/usr/local/bin/docker-compose stop
TimeoutStartSec=0
[Install]
WantedBy=multi-user.target
the log shows
2022-04-04 22:04:51 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
2022-04-05 01:25:45 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT server 192.168.5.5:1883 (7)
[finish] process exit code 0
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
I have tried:
- removing the custom components
- running without mqtt
- running with mqtt and frigate
- starting manually as user hass
- using healthcheck in yaml (test: [“CMD”, “curl”, “-f”, “http://127.0.0.1:8123”]
- privileged: true
- different “restart” criteria (always, unless-stopped, etc.)
- not using “network_mode: host”
- a lot of other stupid ideas that I forgot to mention …
What other relevant info I shall provide? What totally gets me is, that I have two completely same setup (apart from architecture) - Dietpi, docker-compose, home assistant + mqtt and on one computer it works, on other it does not.
Thanks in advance.