From 194a35f97ee0b5eeb1039b9fbc4b1131ba141635 Mon Sep 17 00:00:00 2001
From: UnrealKazu <9115757+UnrealKazu@users.noreply.github.com>
Date: Mon, 25 Feb 2019 21:53:55 +0100
Subject: [PATCH] Add Docker specific explanation for PS4 component (#8629)

The new PS4 component requires some extra settings from Home Assistant if one is using Docker. I've added an entry in the docs to make sure these settings are clear for those who use Docker.
---
 source/_components/media_player.ps4.markdown | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/source/_components/media_player.ps4.markdown b/source/_components/media_player.ps4.markdown
index 0db9f0f54fb..4b35521c547 100644
--- a/source/_components/media_player.ps4.markdown
+++ b/source/_components/media_player.ps4.markdown
@@ -57,6 +57,9 @@ There are varying methods to perform this, dependent on your OS that is running
 `sudo setcap 'cap_net_bind_service=+ep' /usr/bin/python3.5`
 Replace "/usr/bin/python3.5" with your path to Python that is running Home Assistant.
 
+### {% linkable_title Docker %}
+
+When running Home Assistant using Docker, make sure that the Home Assistant container is discoverable by the PS4. This can be achieved by ensuring that the Home Assistant container uses the `host` network driver (by passing `--net=host` to the container when creating, or adding `network_mode: "host"` to your compose file when using `docker-compose`).
 
 ## {% linkable_title Configuration %}