You stopped Portainer or deleted it entirely? I’ve been running Portainer for over a year now and never had an issue updating until now?
Same problem here.
Is there any way to see where the problem comes from? I don‘t see any issues with my docker.
Update:
Found it
22-10-11 05:21:00 ERROR (MainThread) [supervisor.resolution.evaluations.container] Found image in unhealthy image list 'portainer/portainer-ce' on the host
But still don’t understand it. Portainer is up2date and running without errors.
Even if I deinstall portainer it doesn’t work.
22-10-11 05:37:02 WARNING (MainThread) [supervisor.jobs] 'HomeAssistantCore.update' blocked from execution, system is not healthy
Also am having the same issue as the multiple people above me. Seems my image or container portainer/portainer-ce:latest is bringing up this issue?
Is the solution to completely remove portainer, update home assistant, re-install portainer latest? Is this necessary? I feel like this is a false error
Also would like to add I am using portainer:latest, which for me is 2.15.0
same problem, can’t upgrade to core-2022.10.3. docker version 20.10.18
2022-10-11 08:39:55.068 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [2586092520] Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, system is not healthy
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 303, in async_install
await async_update_core(self.hass, version=version, backup=backup)
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 45, in _wrapper
raise HassioAPIError(data["message"])
homeassistant.components.hassio.handler.HassioAPIError: 'HomeAssistantCore.update' blocked from execution, system is not healthy
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 202, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1738, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1775, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 207, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 678, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 931, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 715, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 154, in async_install
await entity.async_install_with_progress(version, backup)
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 413, in async_install_with_progress
await self.async_install(version, backup)
File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 305, in async_install
raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, system is not healthy
1 Like
Any of you, who is running Portainer:
The issue comes from Supervisor and it’s latest PRs. The above PR has been added at 2022.9.2 to Supervisor.
But at that time Supervisor was flagging the system as unhealthy only. Since that, another feature has been added to Supervisor, which is if Supervisor flags the system unhealthy, then it blocks the update of core, add-ons, etc.
My understanding would be if you run Portainer, then the system should be flagged as Unsupported and not Unhealthy, as unhealthy flag is now blocking any updates.
1 Like
Hi. I have the same issue, problem with docker. I removed the portainer and now system is ok. Update from 2022.10.2 to 2022.10.3 is successfull.
The second linked pr is about the new auto update feature. It has nothing to do with unhealthy check. Updates have always been blocked when the system is deemed to be unhealthy. I don’t even know how long ago that was added. This pr in November 20202 added the job infrastructure and it included an unhealthy check that blocked updates. So it’s at least that old.
The only thing new here is the first PR you linked. That’s what added portainer to the “unhealthy images” list.
Incorrect. Running a container which is not supervisor or something started by supervisor is not supported. However running container orchestration software like portainer marks the system as unhealthy since it starts other containers and can change almost anything about docker in ways that break supervisor. Portainer isn’t the only one, the list of container orchestration software that has come up in issues and now marks the system as unhealthy is here:
But isn’t the unsupported state should be considered for issues?
Also Portainer isn’t provided as a Community Add-on?
Can anybody tell me why Home Assistant wants to block portainer? Never hat a problem with it…
same question. seems to come with the latest supervisor update
Now I could solve it.
sudo docker stop portainer
sudo docker restart hassio_supervisor
But this is an error, isn’t it? I don’t see a reasonable sense why portainer should be a party crasher. Issue, ok. But an error?
1 Like
let the people decide if portainer is an issue or not. To be honest, this seems to me too strict.
It was running for years and now I’m not able to update anymore
4 Likes
Just read this thread…
Still I think this change misses the target, I assume that the unhealthy/unsupported info is to tell users if you don’t run HA according to official configuration you won’t get support, right?
Blocking HA from execution is another thing, you stop users from doing stuff they want to do, even if they are well aware they’re doing it at their own risk and they won’t be eligable for any kind of support.
There’s probably going to be a lot of complaints about this.
12 Likes
don’t need to remove portainer.
sudo docker stop portainer
sudo docker restart hassio_supervisor
Update HA and then you can start portainer again
(sudo docker start portainer)
21 Likes
ah, thanks for the hint
Thanks, I’ve updated my post.
1 Like
here is another workaround
4 Likes
Also, no need to reboot host,
sudo docker restart hassio_supervisor
is enough.
1 Like
…now updating. Evien with docker 20.10.5 (dont need to meet docker 20.10.17 for healthy from docs).
Clearly Portainer was the issue HA was having for this update. I will start portainer as soon as I finish my updates. Never have a problem with it.
docker container list
(my portainer image alias was agitated_johnson)
docker container stop agitated_johnson
docker container restart hassio_supervisor
(back to HA and update)
docker container restart hassio_supervisor
docker container start agitated_johnson
2 Likes