Build a private repository using register images in CoreOS

Source: Internet
Author: User

Build a private repository using register images in CoreOS

Docker supports registry to support image distribution and update management. This greatly facilitates users.

The official website dockerhub is provided as a public centralized repository. However, local access to dockerhub is often slow, and many times we need a local private repository for internal use only.

There are many articles about how to create and use a local repository. However, these articles either have outdated content or provide incorrect configurations, resulting in failure to create a repository. This article describes how to create a local Repo using a register Image Based on the CoreOS system.

1. Use registry to start a private repository container
Docker run-d-p 5000: 5000-v/root/my_registry:/tmp/registry
Note: If the registry container is not installed before, a registry container is automatically downloaded and started to create a local private repository service. By default, the repository is created in the/tmp/registry directory of the container. You can use the-v parameter to store the image file in a specified local path (for example, in the local directory/root/my_registry ).

2. push an image to a private Repository
After the register image is started, upload the register image to the local repository for testing.

Note: According to the IP address and Port of the host where the registry container is started in step 1, push the local container of an environment.

Localhost images # docker push 5000/register
The push refers to a repository [ 5000/register] (len: 1)
Sending image list
Pushing repository 5000/register (1 tags)
E9e06b06e14c: Image successfully pushed
A82efea989f9: Image successfully pushed
37bea4ee0c81: Image successfully pushed
07f8e8c5e660: Image successfully pushed
1f4ab7282e19: Image successfully pushed
0e4483abe66b: Image successfully pushed
C6153b5d8f1f: Image successfully pushed
2bc4611f2ed7: Image successfully pushed
30887473610f: Image successfully pushed
3f8e22c413b1: Image successfully pushed
22b1c756fa19: Image successfully pushed
90607d8d09d1: Image successfully pushed
4f4a5acb19eb: Image successfully pushed
204704ce3ed: Image successfully pushed
Pushing tag for rev [204704ce3133] on {http: // 5000/v1/repositories/register/tags/latest}

Directory structure of the host my_registry

Localhost my_registry # ls-R
Images repositories

20172bc4611f2ed7611f46c4aaee05e34b7a490671c79c41b827dc168377da95b041 then
201737bea4ee0c816e3a3fa025f36450ef8ef0817b3f8fcd7b49eb7b26064f647bb0 then
204704ce31375bcf4afecf672563b4881bbef0d59135c68d273235bb7254fb4b 201710000large

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer

_ Checksum ancestry json layer



_ Index_images json tag_latest taglatest_json

Questions about https

Root @ gerryyang :~ # Docker push 5000/Ubuntu_sshd_gcc_gerry: 14.04
FATA [0002] Error: Invalid registry endpoint https: // 5000/v1/: Get https: // 5000/v1/_ ping: EOF. if this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add' -- insecure-registry 5000 'to the daemon's arguments. in the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at/etc/docker/certs. d/ 5000/ca. crt


Vi/usr/lib/systemd/system/docker. service

Modify the content as follows:

Description = Docker Application Container Engine
Documentation =
Afterappsnetwork.tar get docker. socket
Requires = docker. socket

Type = Policy
EnvironmentFile =-/etc/sysconfig/docker
EnvironmentFile =-/etc/sysconfig/docker-storage
ExecStart =/usr/bin/docker-d -- insecure-registry 5000-H fd: // $ OPTIONS $ DOCKER_STORAGE_OPTIONS
Maid = 1048576
LimitNPROC = 1048576

Wantedbypolicmulti-user.tar get

In CoreOS, method 1 may encounter/usr/lib/systemd/system/docker. when the service file ReadOnly cannot be modified, You can manually start and add the -- insecure-registry Parameter
Localhost ~ #/Usr/lib/coreos/dockerd -- daemon -- insecure-registry 5000

3. Private repository Query Method
Curl http: // 5000/v1/search
Note: Use curl to view images in the repository 5000. You can view ubuntu_sshd_gcc_gerry in the result, indicating that the upload is successful.

4. access and download private repository images from other machines
Manually start docker: localhost ~ on the client ~ #/Usr/lib/coreos/dockerd -- daemon -- insecure-registry 5000
Run the pull command
Localhost ~ # Docker pull 5000/jdk7
Pulling repository 5000/jdk7
134625e9d4d7: Download complete
134625e9d4d7: Pulling image (latest) from 5000/jdk7
6941 bfcbbfca: Download complete
41459f052977: Download complete
Fd44297e2ddb: Download complete
40eba1bcf993: Download complete
E60bdcf6f45f: Download complete
367c013cf9ca: Download complete
81812b96beec: Download complete
776f6d47bdf7: Download complete
2c96f979a63a: Download complete
F33b1fffe108: Download complete
71f589de03a8: Download complete
2115aa302043: Download complete
6a498e83fe1b: Download complete
591be66f0e03: Download complete
C468a9de6202: Download complete
A510d6919954: Download complete
14b73f7c3942: Download complete
B591b7e6f5da: Download complete
F1a90a0630e1: Download complete
Unzip a069bbe25: Download complete
Status: Downloaded newer image for 5000/jdk7: latest

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.