diff --git a/source/getting-started/install.rst b/source/getting-started/install.rst
index ca450fb..18bb406 100644
--- a/source/getting-started/install.rst
+++ b/source/getting-started/install.rst
@@ -281,6 +281,7 @@ The installation of Exegol on Linux, macOS and Windows are very similar. It can
         If not, remember that pip installs binaries in a **dedicated** local folder, which then **must** be in the ``PATH`` environment variable.
         Try to fix your pip installation: `Linux <https://stackoverflow.com/a/62823029>`__ | `MacOS <https://stackoverflow.com/a/43368894>`__ | `Windows <https://builtin.com/software-engineering-perspectives/pip-command-not-found>`__
 
+.. _install_exegol_privileges:
 
 3. Run Exegol with appropriate privileges
 -----------------------------------------
diff --git a/source/getting-started/troubleshooting.rst b/source/getting-started/troubleshooting.rst
index 23b692e..e49789e 100644
--- a/source/getting-started/troubleshooting.rst
+++ b/source/getting-started/troubleshooting.rst
@@ -23,7 +23,10 @@ There are multiple checks to do to make sure Docker works properly.
 
     .. tab:: Docker permissions
 
-        Make sure the Docker permissions are consistent with the Exegol permissions. For instance, if you need ``sudo`` rights to use Docker, you'll most likely need ``sudo`` to run Exegol smoothly. See :doc:`the Exegol install guidance</getting-started/install>`.
+        Make sure the Docker permissions are consistent with the Exegol permissions.
+        For instance, if you need ``sudo`` rights to use Docker, you'll most likely need ``sudo`` to run Exegol smoothly.
+
+        See :ref:`the Exegol install guidance<install_exegol_privileges>` to use exegol correctly with sudo.
 
     .. tab:: Docker socket