From 94331af79c575cdf82f4e29e883e502917a6ca63 Mon Sep 17 00:00:00 2001
From: homdx <37062532+homdx@users.noreply.github.com>
Date: Wed, 12 Dec 2018 23:56:35 +0300
Subject: [PATCH] SELinux policy instruction

---
 README.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/README.md b/README.md
index d360e65..c8483ae 100644
--- a/README.md
+++ b/README.md
@@ -48,6 +48,11 @@ echo -n "Your password for https://${IP}/admin/ is "
 docker logs pihole 2> /dev/null | grep 'password'
 ```
 
+If you used RHEL based distrubution with SELinux Enforcing policy add to line with volumes :z
+``` -v "${DOCKER_CONFIGS}/pihole/:/etc/pihole/:z" \
+    -v "${DOCKER_CONFIGS}/dnsmasq.d/:/etc/dnsmasq.d/:z" \
+```
+
 **This is just an example and might need changing.**  Volumes are stored in the directory `$DOCKER_CONFIGS` and are recommended for persisting data across docker re-creations for updating images.  The IP lookup variables may not work for everyone, please review their values and hard code IP and IPv6 if necessary.
 
 Two recently added ports to the `docker run` and `docker-compose` examples are port 67 and 443.  Port 67 is for users who wish to have Pi-hole run a DHCP server.  Port 443 is to provide a sinkhole for ads that use SSL.  If only port 80 is used, then blocked HTTPS queries will fail to connect to port 443 and may cause long loading times.  Rejecting 443 on your firewall can also serve this same purpose.  Ubuntu firewall example: `sudo ufw reject https`