docker.io prefix removed while loading images to WRCP (dsr8mr3, dsr8mr2+)

Change-Id: Ib1e1e98dc1d2b032c91f3ba38039a3a8c509a60f
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>

doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst

@@ -169,7 +169,7 @@ value defaults to 1, which defers the configuration to the per-subcloud
 ``/etc/dcmanager/dcmanager.conf`` to override this setting for all subclouds.
 
 CONF.ipmi_capture options:
-    
+
 0: globally disabled
 1: enabled based on rvmc_debug_level
 2: globally enabled
@@ -413,6 +413,40 @@ CONF.ipmi_capture options:
            username: <your_default_registry_username>
            password: <your_default_registry_password>
 
+    **Using the add_docker_prefix flag**
+
+    The ``add_docker_prefix`` flag determines if ``docker.io prefix`` is
+    automatically added to the image names while importing the images. This is
+    useful in handling the custom and platform images.
+
+    - ``add_docker_prefix``: false (default)
+
+      For default image bundle file names (example:
+      ``container-image*.tar.gz``), ``docker.io prefix`` is added to images
+      without a known registry prefix when they are loaded to the Docker
+      cache. For custom image bundle file names (example: ``custom-name.tar.gz``), the
+      image is loaded to the Docker cache without modifying the registry prefix.
+
+    - ``add_docker_prefix``: true
+
+      For both default and custom image bundle file names, ``docker.io prefix``
+      is added to images without a known registry prefix when they are loaded
+      to the Docker cache.
+
+    You can explicitly set the ``add_docker_prefix`` flag in the host overrides
+    file for more granular control over prefixing during the bootstrap or
+    restore operations.
+
+    Example configuration:
+
+    .. code-block::
+
+        add_docker_prefix: true # Enable prefix for custom images
+        add_docker_prefix: false # Disable prefix for custom images
+
+    This flag ensures that images are handled correctly based on their source,
+    providing flexibility for a custom image management.
+
     .. include:: /_includes/installing-a-subcloud-using-redfish-platform-management-service.rest
        :start-after: begin-subcloud-1
        :end-before: end-subcloud-1

doc/source/dist_cloud/kubernetes/restore-a-subcloud-group-of-subclouds-from-backup-data-using-dcmanager-cli-f10c1b63a95e.rst

@@ -47,12 +47,15 @@ the following parameters/options:
     -   ``bootstrap_address``: List of subclouds and their corresponding
         bootstrap addresses for connectivity.
 
+    -   ``add_docker_prefix``: For more details, see
+        :ref:`installing-a-subcloud-using-redfish-platform-management-service`.
+
         .. code-block:: none
 
             bootstrap_address:
               <subcloud_name1>: <subcloud_bootstrap_address1>
               <subcloud_name2>: <subcloud_bootstrap_address2>
-        
+
         .. note::
 
             The ``bootstrap_address`` key is only necessary for the restore of