supervisor: Latest supervisor break updates and snapshots on synology dsm

@Krocko add jobs.json {“ignore_conditions”: [“healthy”]} in the hassio folder just above config. This ignores unhealthy conditions

I tried to add jobs.json file with that values and didn´t work for me, do I need to do anything else?

It works fine for me. See attached screenshot how it should look like. I restarted the supervisor container and now I am able to play with add-ons.

Sad to see this breaking change, too. Yes, Synology uses some old docker version, but it is the most recent version for all synology users out there. Can understand the intention to move forward, but am unhappy to see so many installations break…

The actual FIX is this post: https://github.com/home-assistant/supervisor/issues/2288#issuecomment-738158680

and how I implemented it here: https://github.com/home-assistant/supervisor/issues/2288#issuecomment-738182230

For posterity, I’m keeping this in case its needed by others in the future:

For those searching for a solution here who are NOT as technical (like me) and you’re using Ubuntu or other Linux Supervised Installs, here are detailed steps used to FIX (OK, BYPASS)this problem:

1. find your Home assistant install directory (“hassio”). It will look like the pic below. rt-click Open the dir AS ADMINISTRATOR

2. Create a new file there with all the other json files called jobs.json. or just duplicate one of the existing files and rename it

3. put this one line in that file:

{“ignore_conditions”: [“healthy”]}

1. save it

2. restart the Supervisor Docker container either in Portainer or reboot your system.

I Was successfully able to restore a Snapshot after doing this. All is now well in the Universe. I can now see my chickens are about to lay eggs on each other!

Jeff

Pascal has opened a PR today that will allow people to disable the health check enforcement https://github.com/home-assistant/supervisor/pull/2290 . Possible but not advised.

@frenck wrote

You are mixing up Unsupported VS Unhealty.

It’s not only we users that mixes these up. Log messages and docs mix these up as well, and this led me to look for something else for a couple of hours, so I thought I’d document it for others that find this (this was my first hit when googling for Unhealthy Home Assistant).

My reason for an unhealthy system, as for many others in this thread, was that I was running Watchtower (configured to only control specific, non Home Assistant, containers). I read in the logs and in the docs that it was not supported, and I thought it meant Unsupported in the same way that running on Ubuntu is not supported, but that’s not the case.

In the logs, Supervisor reports Watchtower with a warning (as opposed to critical) and as not supported:

WARNING (MainThread) [supervisor.resolution.evaluations.base] Found images: {‘watchtower’} which are not supported, remove these from the host! (more-info: https://www.home-assistant.io/more-info/unsupported/container)

And if we check the page in the link it says:

If you remove all offending containers from your host and then reload the Supervisor, it will no longer be marked as unsupported for this reason https://www.home-assistant.io/more-info/unsupported/container

Again, running Watchtower will cause the system to be unhealthy, so what the page states is not true.

To fix it, you not only need to stop, and remove the Watchtower container. You actually need to remove the Watchtower image as well, docker rmi imagename.

I hope we in the future will have the ability to somewhere configure “Yes, I know I’m running the unsupported container Watchtower but it’s been configured to not interfere with Home Assistant, so please ignore Watchtower”

10000000% this!

This is exactly my situation as well. I couldn’t have said it better than @HCanber did here.

@Krocko add jobs.json {“ignore_conditions”: [“healthy”]} in the hassio folder just above config. This ignores unhealthy conditions

I’m also seeing this now when I try to upgrade from 0.118.2 to 0.118.3.

I’ve read the attached and although I am running on an unsupported OS (ubuntu) I’ve got the correct docker version and can’t see any other issues in my logs or otherwise.

Operating System Ubuntu 18.04.3 LTS Docker version 19.03.5 Supervisor Version 2020.11.2

can in next releases added disable this check option? so far now all working ok on old docker, and no fresh docker on synology

It cannot, it needs the Docker version specified (or newer) to function correctly.

The challenge from my understanding is that this then eliminates everyone running on a Synology NAS as they have not moved forward beyond 18.09.8. (Unless I am mistaken)

Hi Guys,

same here for me: Debian 9 in ESXi with docker 18.x and hupsakee System unhealthy (and warning that supervisor not in privileged mode)

upgrade debian 10 and docker did not help check networkmanager did not help

but what did help was: https://community.home-assistant.io/t/supervisor-in-privileged-mode/170629 changing the json file cleared all errors 👍 It is easy visualised with portainer - superviser container - Inspect - Hostconfig - Privileged

@frenck, the concept is noble & good maybe a summary why unhealthy could be interesting in the search of a solution. I did not known about that hostconfig.json (and privileged entry) with the supervisor container …

Mario