Unsupported after Supervisor update to 2022.6.2
See original GitHub issueDescribe the issue you are experiencing
Getting unsupported state after suervisor updated to 2022.6.2
Lean more lead to docker configuration - all recomendations are done
https://www.home-assistant.io/more-info/unsupported/docker_configuration
docker daemon config checked. record to grub added. reinstall from package done. host restarted.
no success at the moment
System Health
version | core-2022.6.7 |
---|---|
installation_type | Home Assistant Supervised |
dev | false |
hassio | true |
docker | true |
user | root |
virtualenv | false |
python_version | 3.9.12 |
os_name | Linux |
os_version | 5.18.0-0.bpo.1-amd64 |
arch | x86_64 |
timezone | Europe/Moscow |
Home Assistant Community Store
GitHub API | ok |
---|---|
GitHub Content | ok |
GitHub Web | ok |
GitHub API Calls Remaining | 4668 |
Installed Version | 1.25.5 |
Stage | running |
Available Repositories | 1156 |
Downloaded Repositories | 24 |
Home Assistant Supervisor
host_os | Debian GNU/Linux 11 (bullseye) |
---|---|
update_channel | stable |
supervisor_version | supervisor-2022.06.2 |
agent_version | 1.2.2 |
docker_version | 20.10.17 |
disk_total | 467.0 GB |
disk_used | 48.3 GB |
healthy | true |
supported | failed to load: Unsupported |
supervisor_api | ok |
version_api | ok |
installed_addons | Samba share (10.0.0), File editor (5.3.3), RPC Shutdown (2.2), Log Viewer (0.14.0), Home Assistant Google Drive Backup (0.108.2), IDE (2.2.0), Grafana (7.6.0), Mopidy (6e49c79), SSH & Web Terminal (11.0.1), MariaDB (2.4.0), Nginx Proxy Manager (0.12.0), AppDaemon (0.9.0), Check Home Assistant configuration (3.11.0), Frigate NVR (3.1), Portainer (2.14.0), Vaultwarden (Bitwarden) (0.17.0), chrony (2.4.0), Samba Backup (5.1.1), Terminal & SSH (9.4.0), ESPHome (dev) (dev), ESPHome (2022.6.2), Studio Code Server (5.1.2), Uptime Kuma (0.1.0), RTSPtoWeb - WebRTC (1.2.2) |
Dashboards
dashboards | 1 |
---|---|
resources | 9 |
views | 22 |
mode | yaml |
Recorder
oldest_recorder_run | July 4, 2022 at 12:22 |
---|---|
current_recorder_run | July 6, 2022 at 12:49 |
estimated_db_size | 5594.80 MiB |
database_engine | postgresql |
database_version | 14.4 |
What is the used version of the Supervisor?
supervisor-2022.06.2
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Debian
What is the version of your installed operating system?
5.18.0-0.bpo.1-amd64
What version of Home Assistant Core is installed?
core-2022.6.7
Steps to reproduce the issue
not known
Anything in the Supervisor logs that might be useful for us?
no errors in supervisor log
Additional information
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Updated to latest supervisor and despite mentioned changes ...
I updated the supervisor to supervisor-2022.06.2 on my otherwise up to date HA supervised setup on Debian bullseye (which is btw up to...
Read more >Help with Supervisor not loading and Unhealthy/Unsupported ...
Supervisor update -- Error: No supervisor update available - 2022.10.0. After that I also grabbed Supervisor and Core logs.
Read more >Bug listing with status RESOLVED with resolution OBSOLETE ...
... Bug:216305 - "Linux >= 2.6.22 and filesystem subtypes" status:RESOLVED ... tty7 since xorg update" status:RESOLVED resolution:OBSOLETE severity:normal ...
Read more >VMware Cloud Director 10.3.3.1 Release Notes
Workaround: Update the /opt/vmware/appliance/bin/setupvcd.sh script with the following commands. #$VCLOUD_HOME/bin/configure --unattended- ...
Read more >Training - AcqDemo
AcqDemo CCAS for Supervisors Briefing – Participant Guide (Oct 2022) ... either because the server or network failed or because the format is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So looks like the issue is solved - with “sudo update-grub” - forgot to did it earlier this day. It is also missing in doc
https://www.home-assistant.io/more-info/unsupported/docker_configuration#the-solution
I believe the issue is the lack of " before and after the text.
Try GRUB_CMDLINE_LINUX_DEFAULT=“systemd.unified_cgroup_hierarchy=false”