DOCSP-42444 updated troubleshooting page with podman error (#714)

Author: kyuan-mongodb

source/atlas-cli-changelog.txt

@@ -27,6 +27,8 @@ Released 25 July 2024
   and :compass:`Compass </>` on Windows.
 - Updates the :ref:`atlas-deployments-setup` command to always use the
   latest image when creating a new local deployment.
+- Drops support for MongoDB 6.0 for local deployments.
+- Drops support for local deployments created with earlier versions of the {+atlas-cli+}.
 - Fixes a bug in the :ref:`atlas-deployments-setup` command where the
   {+atlas-cli+} deletes an existing local deployment when you run this
   command twice for the same deployment.

source/troubleshooting.txt

@@ -201,6 +201,38 @@ Alert Config Not Deleted
 This error might appear if the {+atlas-cli+} can't delete the alert
 configuration specified by the ID. 
 
+podman not found
+~~~~~~~~~~~~~~~~
+
+This error appears if you try to run an ``atlas deployments`` command
+inside our official docker container, ``mongodb/atlas`` in v1.26 or
+later. Instead, follow the steps decribed in
+:ref:`atlas-cli-deploy-docker`.
+
+You should inspect past containers in your {+cluster+} with the
+following command:
+
+.. code-block::
+
+   podman ps -a
+
+Then, remove any that start with ``mongod`` or ``mongot`` with the
+following command:
+
+.. code-block::
+
+   podman container rm -f -v <name or ID>
+
+.. tip::
+
+   You can safely uninstall podman if you're on MacOS.
+
+   If you installed podman with homebrew, use this command to uninstall:
+
+   .. code-block::
+
+      brew uninstall podman
+
 Configuration Errors
 --------------------