From 3bd6f907a9ab59b26dbf29bd163c8c475f3ed9ec Mon Sep 17 00:00:00 2001
From: Michael Stanclift <3002053+vmstan@users.noreply.github.com>
Date: Wed, 29 Sep 2021 16:13:39 -0500
Subject: [PATCH] Updated System Requirements (markdown)

---
 System-Requirements.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/System-Requirements.md b/System-Requirements.md
index c0c7a50..a81886f 100644
--- a/System-Requirements.md
+++ b/System-Requirements.md
@@ -9,7 +9,7 @@ The main requirement is Gravity Sync requires at least two separate Pi-hole 5.x
 ### Containerized Pi-hole
 
 - Your Pi-hole installs can be a Docker container deployment as of Gravity Sync 3.1.
-- Beta support for Podman as a container engine has been introduced starting in Gravity Sync 3.3.
+- Support for Podman as a container engine has been introduced starting in Gravity Sync 3.3.
 - Gravity Sync will run directly on the host OS, and not inside of the container image.
 - Only the [official Pi-hole Docker image](https://hub.docker.com/r/pihole/pihole) is supported.
 - In addition to the officially supported Linux distributions as outlined above, when using a container engine, host OS deployments on more container oriented distributions such as [VMware Photon OS](https://vmware.github.io/photon/) may be used, so long as they’re able to run the Gravity Sync specific requirements below.
@@ -55,6 +55,12 @@ apt update && apt install sqlite3 sudo git rsync ssh
 dnf install sqlite3 sudo git cronie rsync ssh
 ```
 
+### Photon OS
+
+```
+tdnf install sqlite3 sudo git cronie rsync ssh
+```
+
 ## Pi-hole Architecture
 
 You will need to designate one Pi-Hole as primary and at least one as secondary.