Configure a Booster for Installation

If you have trouble downloading images from dockerhub.io, it is highly recommended that you configure a registry mirror (i.e. booster) beforehand to speed up downloads. You can refer to the official documentation of Docker or follow the steps below.

Get a Booster URL

To configure the booster, you need a registry mirror address. See the following example to see how you can get a booster URL from Alibaba Cloud.

1. Log in to the console of Alibaba Cloud and enter “container registry” in the search bar. Click Container Registry in the drop-down list as below.

   

2. Click Image Booster.

   

3. You can find the Booster URL in the image below as well as the official guide from Alibaba Cloud to help you configure the booster.

   

Set the Registry Mirror

You can configure the Docker daemon directly or use KubeKey to set the configuration.

Configure the Docker daemon

Note

Docker needs to be installed in advance for this method.

1. Execute the following commands:

   sudo mkdir -p /etc/docker

   sudo vi /etc/docker/daemon.json

2. Add the registry-mirrors key and value to the file.

   {
     "registry-mirrors": ["https://<my-docker-mirror-host>"]
   }

   Note

   Make sure you replace the address within the quotation mark above with your own Booster URL.

3. Save the file and reload Docker by executing the following commands so that the change can take effect.

   sudo systemctl daemon-reload

   sudo systemctl restart docker

Use KubeKey to set the registry mirror

1. After you create a config-sample.yaml file with KubeKey before installation, navigate to registry in the file.

   registry:
       registryMirrors: [] # For users who need to speed up downloads
       insecureRegistries: [] # Set an address of insecure image registry. See https://docs.docker.com/registry/insecure/
       privateRegistry: "" # Configure a private image registry for air-gapped installation (e.g. docker local registry or Harbor)

2. Input the registry mirror address above and save the file. For more information about the installation process, see Multi-node Installation.

Note

If you adopt All-in-One Installation, refer to the first method because a config-sample.yaml file is not needed for this mode.