Create a private Docker registry pit

1. Create a private Docker registry:

Docker run-d-P 5000:5000 -v/opt/data/registry:/tmp/registry --name Registry Registry:2

Shell script to clean out expired containers:

#!/bin/bash
Docker stop $ (Docker ps-a-Q)
Docker RM $ (Docker ps-a-Q)

2. To create a Docker registry, if you do not use the default HTTPS format, all clients and server must have the--INSECURE-REGISTRY flag set to successfully use the push and pull commands.

Note: There is currently no solution for Windows Docker machine, but the Google solution will pass in the-insecure-registry parameter when creating virtual machine.

Linux System specific error messages:

[email protected] ~]# Docker pull 42.62.101.83:5000/busybox
Using default Tag:latest
Error response from Daemon:get https://42.62.101.83:5000/v1/_ping:tls:oversized record received with length 20527

The following are the setup steps for CentOS:

Back up the original service: Cp/usr/lib/systemd/system/docker.service/usr/lib/systemd/system/docker.service.bak

Change Service Content configuration: Vi/usr/lib/systemd/system/docker.service

[Unit]
Description=docker Application Container Engine
Documentation=https://docs.docker.com
After=network.target Docker.socket
Requires=docker.socket

[Service]
Type=notify
# The default is not-use SYSTEMD for cgroups because the delegate issues still
# exists and SYSTEMD currently does not support the Cgroup feature set required
# for containers run by Docker
#ExecStart =/usr/bin/docker daemon-h fd://
Execstart=/usr/bin/docker Daemon --insecure-re Gistry 42.62.101.83:5000-h fd://$OPTIONS $DOCKER _storage_options

Mountflags=slave
limitnofile=1048576
limitnproc=1048576
Limitcore=infinity
Timeoutstartsec=0
# Set delegate yes so, SYSTEMD does not reset the cgroups of Docker containers
Delegate=yes

[Install]
Wantedby=multi-user.target

Effective Service: Systemctl Daemon-reload

Service Docker restart

Create a private Docker registry pit