Fix airgapped optional docs (#6737)

* Fix airgapped optional docs

* Copy airgapped-packages content into packages/prereq

docs/content/en/docs/getting-started/airgapped/airgap-steps.md

@@ -31,6 +31,14 @@ toc_hide: true
 
    <details>
       <summary>Expand for curated packages instructions</summary>
-      <br /> 
-      {{% content "airgap-packages.md" %}}
-   </details>
+   If you are running in an airgapped environment and you set up a local registry mirror, you can copy curated packages from Amazon ECR to your local registry mirror with the following command. 
+
+   The `$BUNDLE_RELEASE_YAML_PATH` should be set to the `eks-anywhere-downloads/bundle-release.yaml` location where you unpacked the tarball from the`eksctl anywhere download artifacts` command. The `$REGISTRY_MIRROR_CERT_PATH` and `$REGISTRY_MIRROR_URL` values must be the same as the `registryMirrorConfiguration` in your EKS Anywhere cluster specification.
+
+   ```bash
+   eksctl anywhere copy packages \
+     --bundle ${BUNDLE_RELEASE_YAML_PATH} \
+     --dst-cert ${REGISTRY_MIRROR_CERT_PATH} \
+     ${REGISTRY_MIRROR_URL}
+   ```
+   </details>

docs/content/en/docs/packages/prereq.md

@@ -118,7 +118,16 @@ If the image downloads successfully, it worked!
 
 ### Prepare for using curated packages for airgapped environments
 
-{{% content "../getting-started/airgapped/airgap-packages.md" %}}
+If you are running in an airgapped environment and you set up a local registry mirror, you can copy curated packages from Amazon ECR to your local registry mirror with the following command. 
+
+The `$BUNDLE_RELEASE_YAML_PATH` should be set to the `eks-anywhere-downloads/bundle-release.yaml` location where you unpacked the tarball from the`eksctl anywhere download artifacts` command. The `$REGISTRY_MIRROR_CERT_PATH` and `$REGISTRY_MIRROR_URL` values must be the same as the `registryMirrorConfiguration` in your EKS Anywhere cluster specification.
+
+```bash
+eksctl anywhere copy packages \
+  --bundle ${BUNDLE_RELEASE_YAML_PATH} \
+  --dst-cert ${REGISTRY_MIRROR_CERT_PATH} \
+  ${REGISTRY_MIRROR_URL}
+```
 
 Once the curated packages images are in your local registry mirror, you must configure the curated packages controller to use your local registry mirror post-cluster creation. Configure the `defaultImageRegistry` and `defaultRegistry` settings for the `PackageBundleController` to point to your local registry mirror by applying a similar `yaml` definition as the one below to your standalone or management cluster. Existing `PackageBundleController` can be changed, and you do not need to deploy a new `PackageBundleController`. See the [Packages configuration documentation]({{< relref "./packages/#packagebundlecontrollerspec" >}}) for more information.