diff --git a/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/_index.md b/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/_index.md
index 1de5cadd416..db1f0b51e2a 100644
--- a/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/_index.md
+++ b/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/_index.md
@@ -66,7 +66,7 @@ To access all node templates, an administrator will need to do the following:
 
 Using Rancher, you can create pools of nodes based on a [node template](#node-templates). 
 
-A node template defines the configuration of a node, like what operating system to use, number of CPUs and amount of memory.
+A node template defines the configuration of a node, like what operating system to use, number of CPUs, and amount of memory.
 
 The benefit of using a node pool is that if a node is destroyed or deleted, you can increase the number of live nodes to compensate for the node that was lost. The node pool helps you ensure that the count of the node pool is as expected.
 
@@ -80,6 +80,10 @@ The recommended setup is to have:
 - a node pool with the controlplane node role and a count of at least two
 - a node pool with the worker node role and a count of at least two
 
+**RKE1 downstream cluster nodes in an air-gapped environment:**
+
+By default, Rancher tries to run the Docker Install script when provisioning RKE1 downstream cluster nodes, such as in vSphere. However, the Rancher Docker installation script would fail in air-gapped environments. To work around this issue, you may choose to skip installing Docker when creating a Node Template where Docker is pre-installed onto a VM image. [You can accomplish this by selecting **None** in the dropdown list for `Docker Install URL` under **Engine Options** in the Rancher UI.]({{<baseurl>}}/img/rancher/node-template-engine-options-rke1.png)  
+
 #### Node Pool Taints
 
 If you haven't defined [taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) on your node template, you can add taints for each node pool. The benefit of adding taints at a node pool is beneficial over adding it at a node template is that you can swap out the node templates without worrying if the taint is on the node template.
diff --git a/static/img/rancher/node-template-engine-options-rke1.png b/static/img/rancher/node-template-engine-options-rke1.png
new file mode 100644
index 00000000000..700a3cdd4b1
Binary files /dev/null and b/static/img/rancher/node-template-engine-options-rke1.png differ
diff --git a/static/img/rancher/node-template-engine-options-rke1.png:Zone.Identifier b/static/img/rancher/node-template-engine-options-rke1.png:Zone.Identifier
new file mode 100644
index 00000000000..ea9e448db5d
--- /dev/null
+++ b/static/img/rancher/node-template-engine-options-rke1.png:Zone.Identifier
@@ -0,0 +1,3 @@
+[ZoneTransfer]
+ZoneId=3
+HostUrl=https://user-images.githubusercontent.com/98505743/166626035-fafc732a-efe6-4a98-9009-89abfbcf34c2.png