Remove Docker usage instructions from running.rst to streamline documentation

Author: calvinp0

docs/source/running.rst

@@ -37,40 +37,6 @@ input file, and internally ARC treats them the same.
 Other than the file name, the difference is that the restart file
 was automatically generated.
 
-Running via Docker
-^^^^^^^^^^^^^^^^^^
-
-The published Docker image includes ARC and RMG along with convenience entrypoints.
-Bind-mount your working directory and pass an input file path that exists inside
-the container. For best write access on bind mounts, pass your host UID/GID as
-``PUID``/``PGID`` (the entrypoint remaps the ``mambauser`` account).
-
-Run ARC non-interactively::
-
-    docker run --rm \
-        -v "$PWD:/work" -w /work \
-        -e PUID=$(id -u) -e PGID=$(id -g) \
-        laxzal/arc:latest arc my_case/input.yml
-
-Run RMG non-interactively::
-
-    docker run --rm \
-        -v "$PWD:/work" -w /work \
-        -e PUID=$(id -u) -e PGID=$(id -g) \
-        laxzal/arc:latest rmg my_case/input.py
-
-Open an interactive shell::
-
-    docker run --rm -it \
-        -v "$PWD:/work" -w /work \
-        -e PUID=$(id -u) -e PGID=$(id -g) \
-        laxzal/arc:latest
-
-If you need a fully manual invocation inside the container, use
-``micromamba run -n arc_env python /home/mambauser/Code/ARC/ARC.py input.yml``.
-For job submission, the scheduler client tools must be available in the container
-or accessed via SSH on a remote host.
-
 
 A (very) simple input file might look like this::