hassio-compose

hassio-compose copied to clipboard

Hi. Thanks for your job. I have a problem, when I restart the docker server the docker compose tries to update the monitor and ends up giving error. I prefer that it is not updated, to avoid compatibility problems that I have already had.

the error is this hassio_supervisor | 20-05-02 11:09:27 INFO (MainThread) [supervisor.discovery] Load 0 messages hassio_supervisor | 20-05-02 11:09:27 INFO (MainThread) [supervisor.ingress] Load 0 ingress session hassio_supervisor | 20-05-02 11:09:27 INFO (MainThread) [supervisor.secrets] Load Home Assistant secrets: 1 hassio_supervisor | 20-05-02 11:09:27 INFO (MainThread) [__main__] Run Supervisor hassio_supervisor | 20-05-02 11:09:27 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2 hassio_supervisor | 20-05-02 11:09:27 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 220 hassio_supervisor | 20-05-02 11:09:27 INFO (SyncWorker_14) [supervisor.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag 220. hassio_supervisor | 20-05-02 11:09:48 INFO (MainThread) [supervisor.supervisor] Fetch AppArmor profile https://version.home-assistant.io/apparmor.txt hassio_supervisor | 20-05-02 11:09:48 INFO (MainThread) [supervisor.host.apparmor] Add or Update AppArmor profile: hassio-supervisor hassio_supervisor | 20-05-02 11:09:48 INFO (MainThread) [supervisor.addons] Phase 'initialize' start 0 add-ons hassio_supervisor | 20-05-02 11:09:48 INFO (MainThread) [supervisor.addons] Phase 'system' start 0 add-ons hassio_supervisor | 20-05-02 11:09:48 INFO (MainThread) [supervisor.addons] Phase 'services' start 1 add-ons hassio_supervisor | 20-05-02 11:09:48 WARNING (MainThread) [supervisor.addons.addon] core_duckdns already running! hassio_supervisor | 20-05-02 11:09:53 INFO (MainThread) [__main__] Stopping Supervisor hassio_supervisor | 20-05-02 11:09:53 INFO (MainThread) [supervisor.api] Stop API on 172.30.32.2 hassio_supervisor | 20-05-02 11:09:53 INFO (MainThread) [supervisor.misc.forwarder] Stop DNS forwarding hassio_supervisor | 20-05-02 11:09:53 INFO (MainThread) [supervisor.core] Supervisor is down hassio_supervisor | 20-05-02 11:09:53 INFO (MainThread) [__main__] Close Supervisor hassio_supervisor | 20-05-02 11:09:53 ERROR (SyncWorker_6) [concurrent.futures] exception calling callback for <Future at 0x7f1e9c789c50 state=finished returned bool> hassio_supervisor | Traceback (most recent call last): hassio_supervisor | File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 324, in _invoke_callbacks hassio_supervisor | callback(self) hassio_supervisor | File "/usr/local/lib/python3.7/asyncio/futures.py", line 365, in _call_set_state hassio_supervisor | dest_loop.call_soon_threadsafe(_set_state, destination, source) hassio_supervisor | File "uvloop/loop.pyx", line 1265, in uvloop.loop.Loop.call_soon_threadsafe hassio_supervisor | File "uvloop/loop.pyx", line 635, in uvloop.loop.Loop._call_soon hassio_supervisor | File "uvloop/loop.pyx", line 639, in uvloop.loop.Loop._call_soon_handle hassio_supervisor | File "uvloop/loop.pyx", line 668, in uvloop.loop.Loop._check_closed hassio_supervisor | RuntimeError: Event loop is closed hassio_supervisor | 20-05-02 11:09:53 ERROR (MainThread) [asyncio] Task was destroyed but it is pending! hassio_supervisor | task: <Task pending coro=<Core.start() running at /usr/src/supervisor/supervisor/core.py:124> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/local/lib/python3.7/asyncio/futures.py:351, <TaskWakeupMethWrapper object at 0x7f1e9c697f10>()]>> hassio_supervisor exited with code 0

I hope it can be solved

Thank you!