I’m not able to update
20-10-21 12:37:40 ERROR (SyncWorker_4) [supervisor.docker.interface] Can't install homeassistant/armhf-hassio-supervisor:249 -> 404 Client Error: Not Found ("manifest for homeassistant/armhf-hassio-supervisor:249 not found: manifest unknown: manifest unknown").
anyone facing the same issue?
You can’t choose what version of the supervisor you use.
You have the ability to roll it back, but it will automatically updates itself eventually. You cannot disable automatic updates, so even if you roll back it’s likely to just update itself back to the newest version in a short time. This is an intentional choice by the devs, who have stated many times that the supervisor will always update itself, when it wants to, with no plans to give the users control over these updates.
Has there been any talk of a feature to turn off all automatic updates? Would be incredibly useful for cases where HA is running on mobile data (like RV or boat) with tight data caps.
Right now the only work-around I know of is to modify the dns forwarding of the router to force HA’s update checker to fail.
If you want that level of control, you should look into running the standalone container version.
Do Not Change. /etc/docker/key.json:
It must be. /etc/docker/daemon.json:
sudo nano /etc/docker/daemon.json
{
“log-driver”: “journald”,
“storage-driver”: “overlay2”
}
sudo systemctl restart docker
Perhaps you are out of disk space.
Thx, i will fix it (its working anyway).
I could swear that the docs said to edit key.json instead of daemon.json…
And look here:
https://docs.docker.com/config/containers/logging/journald/
The file daemon.json doesnt exist, i suppose i will have to create it.
I’m running ‘unsupported’ on Ubuntu 20.04.1 LTS currently. Supervisor auto-updated from 247 to 249 on me this am. Clicking the warning message showed a Docker error, and I was able to create the daemon.json file, rebooted my entire NUC and now that warning message is gone.
I still have:
but at least Docker error is gone…
When I do the changes Docker is not starting anymore. I am getting this error.
Running systemctl status docker.service gives this error (RESOLVED):
Edit:
After some playing around I found out that it does not like the storage-driver setting. After doing a docker info I found out it was installed with aufs. When changed to aufs it started as usual again.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-10-21 21:46:17 CEST; 14s ago
Docs: https://docs.docker.com
Process: 727 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 727 (code=exited, status=1/FAILURE)
systemd[1]: Failed to start Docker Application Container Engine.
systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
systemd[1]: Stopped Docker Application Container Engine.
systemd[1]: docker.service: Start request repeated too quickly.
systemd[1]: docker.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Docker Application Container Engine.
systemd[1]: docker.service: Start request repeated too quickly.
systemd[1]: docker.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Docker Application Container Engine.
This is the latest version of Docker CE 19.03.13 on Ubuntu 20.04.1
Well, my instance apparently also auto-updated the Supervisor.
Currently on 249, and it’s now complaining about an unsupported installation, because Network Manager is apparently missing.
Thing is, this is a stock Supervised install running on Debian (on a pve host), never fiddled with any settings, so I have no idea why this might have happened.
The suggested remediation on the Network Manager page is re-running the install script. Is it safe to do it in a production system? Will I lose any of my add-ons or data, if I run the script again? And most importantly, since the system was actually installed by that same script, will the error get fixed?
Thanks for any help you guys can give!
You could just ignore it?
If you rerun the script it will be fine. It will just change a couple of docker settings and restart the service which will fix the error.
Thanks! I’ll try that out later today.
Amazing response time, by the way! 
I am very new to home assistant only installing about a week ago, since the latest update I am unable to access any of my add-ons and am also unable to access the supervisor tab.
HA is installed on a Raspberry Pi4. Really unsure how I am going to fix this - any advice would be welcome.
I am not super technical so hopefully there is a simple solution.
Quick: reboot the device, might not work
Not quick: Create a separate thread on this forum, or join discord https://discord.gg/c5DvZ4e
In the new thread, or on discord, provide logs from the help page http://IP_OF_PI:4357
Thanks for the fast response, have tried several reboots with no success. Will try discord or new thread option.
Many users of addon PAI (Paradox Alarm) have reported issues since Supervisor 249 update :
I’ve tried to downgrade Supervisor to version 247 yesterday, it worked but automatically updated back to 249. Is there a way to prevent this automatic update temporarily ?
Thx.
The author of that add-on is working on a fix
I’ve just seen your answer on github ! Thanks ! 