Registry Management

registry management enables you to view, add, and remove registry providers these registry providers will be the source of where docker images of marketplace catalog applications can be pulled when deploying to belden horizon data operations instances docker requires you to connect to a https //docs docker com/registry/deploying/#running a domain registry you can find more information about how to connect to an https //docs docker com/registry/insecure/ the default registries available are https //www docker elastic co https //mcr microsoft com https //hub docker com \[1] return to applications docid\ ya binyxzj3rjz3v1 1pq \[2] add new repository refer to the following parameters to configure for each registry aws ecr name registry description (optional) aws region (optional) aws key id aws secret key azure container registry name registry description (optional) service principal name service subscription identifier client id client secret resource group registry name address enter the location of the registry docker registry name registry description (optional) docker login server enter https //index docker io/v1 docker login user (optional) docker login password (optional) docker ca certificate (optional) paste a ca certificate in the docker ca certificate field if belden horizon data operations is already connected to belden horizon data manager, the ca certificate used for that connection is applied docker skip tls verification (optional) select the check box to bypass the tls security google container registry name google container registry address repository description (optional) json key fie browse to add a key file \[3] edit repository \[4] delete repository