From d6dece293cc127e917f52cb17f648b91cfde65bf Mon Sep 17 00:00:00 2001
From: Franck Nijhof <git@frenck.dev>
Date: Wed, 1 Jun 2022 19:27:34 +0200
Subject: [PATCH] 2022.6: Add missing init system breaking change (#22947)

* 2022.6: Add missing init system breaking change

* More cleanups
---
 .../installation/container/alternative.md     | 48 -------------------
 .../_posts/2022-06-01-release-20226.markdown  | 20 ++++++++
 2 files changed, 20 insertions(+), 48 deletions(-)

diff --git a/source/_includes/installation/container/alternative.md b/source/_includes/installation/container/alternative.md
index c9f1e68dd8e..d5ef764e0eb 100644
--- a/source/_includes/installation/container/alternative.md
+++ b/source/_includes/installation/container/alternative.md
@@ -89,51 +89,3 @@ The steps would be:
 - Your Home Assistant within Docker should now run and will serve the web interface from port 8123 on your Docker host (this will be your Qnap NAS IP address - for example `http://192.xxx.xxx.xxx:8123`)
 
 Remark: To update your Home Assistant on your Docker within Qnap NAS, you just remove container and image and do steps again (Don't remove "config" folder).
-
-If you want to use a USB Bluetooth adapter or Z-Wave USB stick with Home Assistant on Qnap Docker, follow those steps:
-
-#### Z-Wave
-
-- Connect to your NAS over SSH
-- Load cdc-acm kernel module(when NAS restart need to run this command)
-  `insmod /usr/local/modules/cdc-acm.ko`
-- Find USB devices attached. Type command:
-  `ls /dev/tty*`
-  The above command should show you any USB devices plugged into your NAS. If you have more than one, you may get multiple items returned. Like : `ttyACM0`
-
-- Run Docker command:
-
-  ```bash
-  docker run --init --name homeassistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e TZ=Europe/London --device /dev/ttyACM0 {{ site.installation.container }}:stable
-  ```
-
-  `-v` is your configuration path
-  `-e` is set timezone
-
-- Edit `configuration.yaml`
-
-```yaml
-zwave:
-  usb_path: /dev/ttyACM0
-```
-
-That will tell Home Assistant where to look for our Z-Wave radio.
-
-#### Bluetooth
-
-- Connect to your NAS over SSH
-- Run Docker command:
-
-  ```bash
-  docker run --init --name homeassistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e TZ=Europe/London -v /dev/bus/usb:/dev/bus/usb -v /var/run/dbus:/var/run/dbus {{ site.installation.container }}:stable
-  ```
-
-  First `-v` is your configuration path
-  `-e` is set timezone
-
-- Edit the `configuration.yaml` file
-
-```yaml
-device_tracker:
-  - platform: bluetooth_tracker
-```
diff --git a/source/_posts/2022-06-01-release-20226.markdown b/source/_posts/2022-06-01-release-20226.markdown
index 5276e4e1f72..e902ef4926f 100644
--- a/source/_posts/2022-06-01-release-20226.markdown
+++ b/source/_posts/2022-06-01-release-20226.markdown
@@ -464,6 +464,26 @@ the documentation of the specific integration on how to configure this.
 
 {% enddetails %}
 
+{% details "Home Assistant Container" %}
+
+If you run Home Assistant Container in Docker (e.g., using Portainer,
+Docker (Compose), QNAP, and others), please make sure you are not specifying
+an init process. 
+
+This can be an `init` configuration option in your Docker management tools or
+Docker Compose, or the `--init` command line flag on the raw Docker command.
+These should **NOT** be set, as Home Assistant ships with the S6 init system.
+
+While you are at it, make sure you also do not set a `cmd` or `entrypoint`.
+Setting these are not breaking, however, you should not set them.
+
+([@pvizeli] - [#72425]) ([documentation](/installation))
+
+[@pvizeli]: https://github.com/pvizeli
+[#72425]: https://github.com/home-assistant/core/pull/72425
+
+{% enddetails %}
+
 {% details "1-Wire" %}
 
 Using the 1-Wire via SysBus, previously deprecated, has been removed;