There is no support for authenticating to a Docker registry within the peer.
Iy your private registry requires authentication, then you will need to pull the images on the host where the Docker daemon is running prior to running your peer(s).

With Fabric 2.x, you could implement support for this by writing your own external builder / launcher. See https://hyperledger-fabric.readthedocs.io/en/release-2.2/cc_launcher.html?highlight=launcher

-----------------------------------------
Gari Singh
Distinguished Engineer, CTO - IBM Blockchain
IBM Middleware
550 King St
Littleton, MA 01460
Cell: 978-846-7499
garis@...
-----------------------------------------

-----fabric@... wrote: -----
To: fabric@...
From: chintanr97@...
Sent by: fabric@...
Date: 07/17/2020 02:39AM
Subject: [EXTERNAL] [Hyperledger Fabric] Pulling chaincode related image from a private registry #fabric-chaincode #docker #hyperledger-fabric

Hi Team, for the chaincode instantiation we pull the images dynamically from the docker hub. However, let's say if I have chaincode related images (e.g. fabric-ccenv, fabric-baseos, etc.) on a private registry, then how shall the peer code *validate or authenticate* to the registry? Is there any setting in core.yaml or other configuration changes that we can make to achieve that?