Skip to content

Commit

Permalink
Add troubleshoot ref to install doc
Browse files Browse the repository at this point in the history
  • Loading branch information
Dramelac committed Aug 24, 2024
1 parent 9ca5b3d commit fbc0b4b
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 1 deletion.
1 change: 1 addition & 0 deletions source/getting-started/install.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
-----------------------------------------
Expand Down
5 changes: 4 additions & 1 deletion source/getting-started/troubleshooting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit fbc0b4b

Please sign in to comment.