expand docs

docs/developer_guide/docker_images.rst

@@ -75,6 +75,7 @@ and can then run the entrypoint (equivalent to the usual command line usage) on
 
 
 
+.. _developer_docker_details:
 
 Run Docker container on YAML conversion specification environment variable
 --------------------------------------------------------------------------

docs/user_guide/docker_demo.rst

@@ -123,4 +123,25 @@ Voilà! If everything occurred successfully, you should see...
 RClone With Config Docker Demo
 ------------------------------
 
-# TODO
+NeuroConv also supports a convenient Docker image for running data transfers via `Rclone <https://rclone.org>`_.
+
+To use this image, you must first configure the remote locally by calling:
+
+.. code::
+
+    rclone config
+
+And following all interactive instructions (defaults are usually sufficient).
+
+The Docker image requires two environment variables to be set (see :ref:`developer_docker_details` for more details in a related process).
+
+- ``RCLONE_CONFIG``: The full file content of the rclone.conf file on your system. You can find this by calling ``rclone config file``. On UNIX, for example, you can set this variable using ``RCLONE_CONFIG=$(<rclone.conf)`` from the folder containing the file
+- ``RCLONE_COMMAND``: The Rclone command to run. For example, ``remote_name:source_folder destination_folder --verbose --progress --config ./rclone.conf``, where ``remote_name`` is the name used during initial setup through ``rclone config``, ``source_folder`` is the name of the folder you wish to transfer data from on that remote, and ``destination_folder`` is the local folder to transfer the data to.
+
+Then, you can use the following command to run the Rclone Docker image:
+
+.. code::
+
+    docker run -t --volume destination_folder:destination_folder -e RCLONE_CONFIG="$RCLONE_CONFIG" -e RCLONE_COMMAND="$RCLONE_COMMAND" ghcr.io/catalystneuro/rclone_with_config:latest
+
+This image is particularly designed for convenience with AWS Batch (EC2) tools that rely heavily on atomic Docker operations. Alternative AWS approaches would have relied on transferring the Rclone configuration file to the EC2 instances using separate transfer protocols or dependent steps, both of which add complexity to the workflow.

tests/docker_rclone_with_config_cli.py

@@ -91,6 +91,3 @@ def test_direct_usage_of_rclone_with_config(self):
             assert (
                 file_content == "This is a test file for the Rclone (with config) docker image hosted on NeuroConv!"
             ), "The file content does not match expectations!"
-
-    def test_helper_function(self):
-        pass  # TODO