1. A Strange Requirement My boss had a strange requirement: use a single kubeconfig file to fetch all kinds of host status information, such as the process list and process states. My first reaction was that he must not understand containers — how could anyone use them that way, and if you were going to use them that way, why use containers at all?

1. DockerHub Limits In the end, there is no getting around this error: 1 Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit Starting November 2, 2020, DockerHub officially began limiting the pull rate for non-paying users:

1. Typical Use Cases In CI, there is usually a CI Engine responsible for parsing the pipeline and controlling the whole build process, while the actual build is delegated to an Agent. Jenkins and GitLab both work this way. As shown below, there are many kinds of Agents that connect to the CI Engine.

1. Why Deploy Independently with an Image Better SEO With GitHub Pages, deploying a static site is very convenient. Configure it once, and every commit deploys and updates automatically. Add jsDelivr and Cloudflare acceleration on top, and among free options it is already production-ready. Unfortunately, Baidu’s search engine indexes GitHub Pages sites very slowly, or not at all.

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.