1. Github Container Registry On September 1, GitHub announced that Github Container Registry had entered public beta, offering a free, unlimited-capacity Docker image registry service during the testing period. No more worrying about docker.io wiping images out of the blue. How nice, how sweet! GitHub is using hosted code repositories as its entry point and gradually covering the entire R&D toolchain to build a one-stop DevOps platform.

1. Enabling Docker’s experimental Feature First, enable Docker’s experimental feature, so the commands below are available. Edit vim ~/.docker/config.json and add the following: 1 2 3 4 { "experimental": "enabled", "debug": true } Note that this is not the /etc/docker/daemon.json file, and Docker does not need to be restarted. 2. Docker Images Starting with Docker 1.

In an earlier post, Installing Harbor with Helm, I described in detail how to install Ingress and Harbor and finally push an image successfully. There the domain was publicly reachable and the certificate was issued by a certificate authority. In an intranet environment, however, we need to use an internal domain name for access.

1. Multi-Stage Builds Compiling a project requires a set of specific tools, but those tools are not needed at runtime. To reduce the image size, you can build in stages. Build in the first stage, then carry the compiled output into the next stage to produce a smaller image. 1 2 3 4 5 6 7 8 9 10 11 FROM golang:1.

1. Requirements for Building Harbor Harbor hardware requirements: CPU, at least 2 cores, 4 cores is better Mem, at least 4 GB, 8 GB is better Disk, at least 40 GB, 160 GB is better Docker version requirements: 17.06.0 or later To build Harbor on Kubernetes, you can refer to the documentation, Building Harbor with Helm.