# Listing directory to confirm file has content admin@fcc1a71d8f61:~/myregistry$  ls -la total 442368 drwxrwxr-x 1 admin admin 48 Sep 7 20:44  . drwxr-xr-x 1 admin admin 186 Sep 7 15:46  .. -rw-rw-r-- 1 admin admin 2490 Sep 7 15:46 Dockerfile -rw------- 1 admin admin 452978176 Sep 7 20:44  myregistry.tar # Loading the myregistry into Docker  admin@fcc1a71d8f61:~/myregistry$  docker load < myregistry.tar Loaded image: myregistry:latest 6.4 Running a local private registry After you build the private registry image, you start it and make it available for users who must  deploy Docker containers. This section shows how to run an insecure private registry. For  more information about secure private registries, see section 6.5, “Deploying a secure private  registry” on page 120. Complete the following steps for the zCX instance where you built the insecure registry  image. 1. Ensure that you are connected to the zCX instance with SSH. 2. Run the following command to confirm that the private registry image is available:  docker images Example 6-11 shows typical output that indicates that the  myregistry  image is available. Example 6-11 Output of docker images command admin@fcc1a71d8f61:~/myregistry$  docker images REPOSITORY TAG IMAGE ID CREATED SIZE myregistry latest  082be17251ee 4 hours ago 441MB ibm_zcx_zos_cli_image latest  00f61e376fd0 2 days ago 363MB ubuntu latest  f8835575bd80 3 weeks ago 64.8MB s390x/ubuntu 16.04  fcae39a6d474 6 weeks ago 118MB 3. Run the following command to start your private registry server to listen on port 5000. docker run -d -p 5000:5000 --restart=always --name registry myregistry:latest Table 6-2 describes each parameter for the command. Table 6-2 Parameters information Parameter Description -d Run container in background and print container ID -p 5000:5000 Publish a container’s port(s) to the host. The private registry now listens  on port 5000. --restart=always Start this container during system startup --name registry The name of the container  myregistry:latest Image name Chapter 6. Private registry implementation  119