Docker DC/OS registry installation Instructions
- Search for registry in the DC/OS catalog
Review properties
- User login properties
- Registry URL
- External networking
- Storage
Deploy registry package and verify it is running in DC/OS
SSH into the master leader node
dcos node ssh --master-proxy --leaderFrom within the leader master node, perform a test docker login operation on the new cluster. If login successful you will see a message like:
[root@server1 ~]# docker login registry.marathon.l4lb.thisdcos.directory Username: username Password: Error response from daemon: Get https://registry.marathon.l4lb.thisdcos.directory/v1/users/: x509: certificate is valid for localhost, master.mesos, leader.mesos, server1.hdp, 192.168.1.100, 127.0.0.1, 192.168.1.100, not registry.marathon.l4lb.thisdcos.directoryXXX find out why the marathon certificate message reported.
Then do a: docker info to check the repository URL. You should see in the docker info listing a text block like:
Insecure Registries:
127.0.0.0/8
Perform a test installation of the new private Docker DC/OS registry
The final test, while we are still in the master leader, we will want to check is the ability to insert a docker image into the new private registry. To accomplish this we will first pull the nginx docker image, tag it and finally push it to the registry using the following steps:
- Pull the latest nginx image from the docker public repository
[root@server1 ~]# docker pull nginx Using default tag: latest latest: Pulling from library/nginx bc95e04b23c0: Pull complete 110767c6efff: Pull complete f081e0c4df75: Pull complete Digest: sha256:004ac1d5e791e705f12a17c80d7bb1e8f7f01aa7dca7deee6e65a03465392072 Status: Downloaded newer image for nginx:latest- Tag the nginx image
- Validate that the image is in the new repository:
curl --insecure https://registry.marathon.1l41lb.thisdcos.directory:5000/v2/_catalog