Has something changed? I’m now getting the following error in the supervisor log:
20-08-17 11:56:23 ERROR (MainThread) [supervisor.core] Using 'Ubuntu 18.04.2 LTS' as the OS is not supported
I’m running 0.110.3 under VirtualBox. If I restart the VM, hassio_supervisor appears to be running but homeassistant isn’t. If I start homeassistant with portainer, it starts but supervisor crashes and won’t restart.
That error does not make Supervisor not to start. There are already a lot of topics discussing that error.
That was the first thing I checked. A search for “Using ‘Ubuntu 18.04.2 LTS’ as the OS is not supported” brought up nothing related. After this error I get the following:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/docker/api/client.py", line 261, in _raise_for_status
response.raise_for_status()
File "/usr/local/lib/python3.8/site-packages/requests/models.py", line 941, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.40/images/sha256:5d537df894979fb54b97572d8d3a3c3b7928384797dab3624a558c17b7a6e6cf/json
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/local/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/src/supervisor/supervisor/__main__.py", line 47, in <module>
loop.run_until_complete(coresys.core.setup())
File "uvloop/loop.pyx", line 1456, in uvloop.loop.Loop.run_until_complete
File "/usr/src/supervisor/supervisor/core.py", line 148, in setup
if await self.sys_run_in_executor(self.sys_docker.check_denylist_images):
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/supervisor/supervisor/docker/__init__.py", line 239, in check_denylist_images
for image in self.images.list():
File "/usr/local/lib/python3.8/site-packages/docker/models/images.py", line 364, in list
return [self.get(r["Id"]) for r in resp]
File "/usr/local/lib/python3.8/site-packages/docker/models/images.py", line 364, in <listcomp>
return [self.get(r["Id"]) for r in resp]
File "/usr/local/lib/python3.8/site-packages/docker/models/images.py", line 316, in get
return self.prepare_model(self.client.api.inspect_image(name))
File "/usr/local/lib/python3.8/site-packages/docker/utils/decorators.py", line 19, in wrapped
return f(self, resource_id, *args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/docker/api/image.py", line 245, in inspect_image
return self._result(
File "/usr/local/lib/python3.8/site-packages/docker/api/client.py", line 267, in _result
self._raise_for_status(response)
File "/usr/local/lib/python3.8/site-packages/docker/api/client.py", line 263, in _raise_for_status
raise create_api_error_from_http_exception(e)
File "/usr/local/lib/python3.8/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
raise cls(e, response=response, explanation=explanation)
docker.errors.APIError: 500 Server Error: Internal Server Error ("readlink /var/lib/docker/overlay2: invalid argument")
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
I guess it doesn’t pay to search for the exact error. Any ideas on what the subsequent errors might mean then?
There was someone with the same error yesterday.
I think it was this topic :
I tried that but it didn’t help. I reverted to the VirtualBox snapshot I took after I noticed something was wrong, then deleted the docker image being referred to in the error (it was for homeassistant/amd64-hassio-audio:16 which was unused) and restarted HA and now it seems happy. So I guess my problem is fixed, although not really any wiser as to what went wrong. The VM says it’s using 46GB out of 55GB allocated, and it’s on a drive that has 500GB free, so that shouldn’t be an issue.
Thanks for your help.
