The private-registry with ssl on closed network can't communicate with docker.io

I built a private registry with Harbor based on SSL.
I want to communicate though private registry including docker.io and k8s.gcr.io.
So I pushed private containers, docker.io containers and k8s.gcr.io containers images.

The private container images works with private registry.
But, The docker.io container images can’t communicate with private registry.

Micok8s can’t find docker.io container images.
Could you know how to configure docker.io with private registry.

Cluster Environment: Closed Network
Microk8s version : 1.25
Private Regisry : Harbor 2.6.0

The containerd configuation related to docker.io is as follow.

containerd-template.toml

cd /var/snap/microk8s/current/args
vi containerd-template.toml

[plugins.“io.containerd.grpc.v1.cri”.registry]
config_path = “${SNAP_DATA}/args/certs.d”
[plugins.“io.containerd.grpc.v1.cri”.registry.configs]
[plugins.“io.containerd.grpc.v1.cri”.registry.configs.“172.16.6.203”.auth]
username = “admin”
password = “Harbor12345”

cd /var/snap/microk8s/current/args/certs.d/docker.io

vi hosts.toml
server = “https://registry-1.docker.io

[host.“https://172.16.6.203”]
capabilities = [“pull”, “resolve”, “push”]
ca = “/var/snap/microk8s/current/args/certs.d/docker.io/ca.crt”
client = [[“/var/snap/microk8s/current/args/certs.d/docker.io/xxxxx.cert”, “/var/snap/microk8s/current/args/certs.d/docker.io/xxxxx.key”]]