jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-09 18:36:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rename unsupported reason container to software (#19857)

Browse Source
This commit is contained in:
Joakim Sørensen 2021-10-19 11:27:08 +02:00 committed by GitHub
parent 2d37b76c67
commit 64cb50619d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 16 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
source/_redirects
View File

@ -2124,6 +2124,7 @@
/cookbook /examples
/common-tasks/os/#snapshots /common-tasks/os/#backups
/common-tasks/supervised/#snapshots /common-tasks/supervised/#backups
/more-info/unsupported/container /more-info/unsupported/software
# Migrated Community Guides
/cookbook/apache_configuration https://community.home-assistant.io/t/reverse-proxy-with-apache/196942

2
source/more-info/unhealthy/docker.markdown
View File

@ -7,7 +7,7 @@ Docker is at the core of most operations that the Supervisor does, it is importa
The Supervisor will be marked as unhealthy if any of these requirements are not met:
- [Running containers known to cause issues](/more-info/unsupported/container)
- [Running unsupported software](/more-info/unsupported/software)
- [Running an unsupported Docker version](/more-info/unsupported/docker_version)
- [Running the Supervisor under LXC](/more-info/unsupported/lxc)
- [Not running the Supervisor as privileged](/more-info/unsupported/privileged)

17
source/more-info/unsupported/container.markdown
View File

@ -1,17 +0,0 @@
---
title: "Containers known to cause issues"
description: "More information on why certain containers marks the installation as unsupported."
---
## The issue
The Supervisor needs to be the only manager of the containers that it manages, unfortunately, some other containers also take on this role. Worst case, those will auto-update the existing containers to development builds without consideration of the channel you have chosen. Because of this, a few containers known to cause issues, have been added to a denylist that will flag your installation as unsupported.
As stated in [ADR-0014](https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md), running additional software on the host is not supported,
and more containers or other software can be added to the denylist without any notice.
## The solution
You will find a list of offending containers in your Supervisor log.
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.

14
source/more-info/unsupported/software.markdown Normal file
View File

@ -0,0 +1,14 @@
---
title: "Unsupported software"
description: "More information on why running unsupported software marks the installation as unsupported."
---
## The issue
As stated in [ADR-0014](https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md), no additional software, outside of the Home Assistant ecosystem, is installed. This includes but are not limited to standalone containers running on the same host.
Some containers will also conflict with the operations of the Supervisor, if you run any of those your system will also be marked as unhealthy. These containers will be shown in the Supervisor log as errors.
## The solution
Remove any additional software (including standalone containers) you have installed on your host and restart the Supervisor.