Shulou(Shulou.com)06/02 Report--

How to use InsecureRegistry in GitLab CI? for this problem, this article introduces the corresponding analysis and answer in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

First of all, the use of insecure registry is not recommended. After all, there are inherent limitations. If you have to use it, you can configure a command in the services layer, which is the simplest, for example:

Services:-name: docker:dind command: ["--insecure-registry=myregistry:5000"]

Due to the limit on the number of words left, let's stop here for a detailed explanation.

The actual effect of this practice is as follows:

(Tao) ➜kubernetes git: (master) ✗ sudo docker run-d-privileged-name dind docker:dind-insecure-registry= "myregistry:5000" 8fb68865638ebc65255bb568fbe1fd6b4ed4fca771075d8e55ebbbbdf0aef6d2 (Tao)➜ kubernetes git: (master) ✗ sudo docker top dindUID PID PPID C STIME TTY TIME CMDroot 18270 18252 1 11:27? 00:00:00 dockerd-host=unix:///var/run/docker.sock-host=tcp://0.0.0.0:2375-insecure-registry=myregistry:5000root 18328 18270 0 11:27? 00:00:00 docker-containerd-- config / var/run/docker/containerd/containerd.toml 's answers to the questions on how to use InsecureRegistry in GitLab CI are shared here I hope the above content can help you to a certain extent, if you still have a lot of doubts to be solved, you can follow the industry information channel to learn more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.