From 64cb50619d162fa4b7dba3cbac63ca71dbae69e8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joakim=20S=C3=B8rensen?= Date: Tue, 19 Oct 2021 11:27:08 +0200 Subject: [PATCH] Rename unsupported reason container to software (#19857) --- source/_redirects | 1 + source/more-info/unhealthy/docker.markdown | 2 +- source/more-info/unsupported/container.markdown | 17 ----------------- source/more-info/unsupported/software.markdown | 14 ++++++++++++++ 4 files changed, 16 insertions(+), 18 deletions(-) delete mode 100644 source/more-info/unsupported/container.markdown create mode 100644 source/more-info/unsupported/software.markdown diff --git a/source/_redirects b/source/_redirects index e5ebf1c7564..59755bccdea 100644 --- a/source/_redirects +++ b/source/_redirects @@ -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 diff --git a/source/more-info/unhealthy/docker.markdown b/source/more-info/unhealthy/docker.markdown index 8050c6255ca..dbef8e317d0 100644 --- a/source/more-info/unhealthy/docker.markdown +++ b/source/more-info/unhealthy/docker.markdown @@ -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) diff --git a/source/more-info/unsupported/container.markdown b/source/more-info/unsupported/container.markdown deleted file mode 100644 index 570f0ed747f..00000000000 --- a/source/more-info/unsupported/container.markdown +++ /dev/null @@ -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. diff --git a/source/more-info/unsupported/software.markdown b/source/more-info/unsupported/software.markdown new file mode 100644 index 00000000000..0de0fcb1d60 --- /dev/null +++ b/source/more-info/unsupported/software.markdown @@ -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.