@rwlove wrote:
When I build a derivative Docker image ‘FROM homeassistant/home-assistant:0.108.0’ it fails to run. This also happened to me with v0.107.7. Everything works fine in v0.106.2.
I tried to file a defect against Hass.io, but I was told that was I was doing was not Hass.io.
Has anyone encountered this problem?
Is there an official place to file a defect against the Home Assistant Docker images?
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] udev.sh: executing…
starting version 3.2.9
[15:46:02] INFO: Update udev information
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2020-04-08 15:46:04 INFO (MainThread) [homeassistant.bootstrap] Config directory: /config
2020-04-08 15:46:04 INFO (SyncWorker_0) [homeassistant.config] Upgrading configuration directory from 0.7.7 to 0.108.0
Testing configuration at /config
2020-04-08 15:46:05 INFO (SyncWorker_4) [homeassistant.loader] Loaded homeassistant from homeassistant.components.homeassistant
…
2020-04-08 15:46:05 INFO (MainThread) [homeassistant.setup] Setting up logger
[cmd] python exited 0
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
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.
Posts: 1
Participants: 1