Failed to Download Some Binary Components or Container Images During KubeSphere Installation

Symptom

During the KubeSphere installation, some binary components or container images fail to be downloaded. The following information is displayed:

Failed to download xxx binary

pull image failed

Key Process and Cause Analysis

The download source is from websites outside China, so that the connection is subject to network fluctuation. In addition, Docker Hub has a limit on the number of downloads when you are not logged in. The error message "You have reached your pull rate limit." is displayed.

Conclusion and Solution

Ensure that the network connection is normal and try to run the failed deployment command for multiple times. After the binary components or container images are successfully downloaded for the first time, you do not need to re-download them for future reinstallation. If the number of downloads reaches the limit, you need to log in to Docker Hub through the CLI to download the container image again. If you cannot download images from dockerhub.io, you are advised to configure Docker image acceleration in advance.