From 193492d99d9cfee486384cf3a0ec0f17373a2861 Mon Sep 17 00:00:00 2001 From: Mike Degatano Date: Thu, 22 Sep 2022 03:48:16 -0400 Subject: [PATCH] Unsupported restart policy information (#24206) --- .../unsupported/restart_policy.markdown | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 source/more-info/unsupported/restart_policy.markdown diff --git a/source/more-info/unsupported/restart_policy.markdown b/source/more-info/unsupported/restart_policy.markdown new file mode 100644 index 00000000000..3cb7a53943c --- /dev/null +++ b/source/more-info/unsupported/restart_policy.markdown @@ -0,0 +1,26 @@ +--- +title: "Restart policy" +description: "More information on why changing the docker restart policy for containers marks the system as unsupported." +--- + +## The issue + +Supervisor needs to start the containers it manages for addons, plugins and Home Assistant in the +correct order after a system reboot. Changing the restart policy it sets on those containers may +cause them to start in the wrong order and create errors. + +## The solution + +If the restart policy of observer was changed, fix it from the host shell with this: + +```sh +docker update hassio_observer --restart always +``` + +For everything else, the restart policy can be fixed with the following command: + +```sh +docker update --restart no +``` + +The supervisor log should contain a list of container names with incorrect restart policies.