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

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.

1. What Problem S2I Solves It is foreseeable that a large number of applications will be deployed as containers in the future. Container platforms care about images and containers, while application development cares about business code, and ultimately the code needs to be deployed as an image. From code to image — that is Source To Image, or S2I.