0a954493d5a033ad97697eed711175c017d74d22
gperez2
  Thu Jul 17 16:04:28 2025 -0700
Adding docker page link to product README.txt and mirror.html help page, refs #34915

diff --git src/product/README.txt src/product/README.txt
index ae7c20ab66c..6a10ae08194 100644
--- src/product/README.txt
+++ src/product/README.txt
@@ -44,31 +44,33 @@
         * If your hub includes a high number of
         annotation files or HAL (multiple alignment) files and is located far
         from Santa Cruz, the display performance of assembly hubs may be slower than a local mirror. This issue
         can be resolved by using a UCSC mirror closer to the assembly
         hub (e.g. use genome-euro.ucsc.edu for assembly hubs located on servers in Europe, 
         or genome-asia.ucsc.edu for those in Asia). Alternatively, you can improve performance 
         by  moving your hub data to a webspace
         provider closer to Santa Cruz or by using a content distribution network,
         where all content is mirrored and the closest location is chosen by your provider.
 
 3.  **Install locally with the Genome Browser installation script (GBIC)**
 
     We recommend this only if none of the above options fulfill your needs. Our
     [GBIC installation](https://genome.ucsc.edu/goldenpath/help/gbic.html) script 
     will install a full local mirror of the UCSC website,
-    for the assemblies you select. We support mirror site installations as time
+    for the assemblies you select. GBiC can also be used as a Docker container. See the
+    [Docker installation instructions](#docker-installation-instructions) below.
+    We support mirror site installations as time
     allows, and have many functional mirrors of the Genome Browser worldwide. For
     details, see the [section below](#installing-a-genome-browser-locally-with-the-gbic-installer).
 
     * Pros:
         * Relatively simple to install on a virtual machine or cloud instance: just run the script.
         * Best performance when rendering local BAM/bigWig/bigBed files.
         * For commercial users: easier click-through licensing compared to a full multi-seat, manual license.
     * Cons:
         * To keep up with changes in the Genome Browser, you will have to install 
           linux packages and update the linux distribution yourself in the future 
           and run the installation script with the 'update' command if you want to
           take advantage of new features in the Genome Browser.
         * Preferably run on a linux server that is not used otherwise.
         * By default requires opening at least three outgoing ports to UCSC for 
           MariaDB and BLAT in your firewall. Once all data is downloaded and BLAT