Harbor + containerd v2: Fixing HTTP Registry Errors
containerd v2 broke insecure HTTP registry config. Here is the exact fix. After upgrading to containerd v2, image pulls from a private Harbor registry over HTTP failed: Create the hosts config directory for your registry IP: Create Restart containerd on all nodes: Verify with: The Error
http: server gave HTTP response to HTTPS client The Fix
mkdir -p /etc/containerd/certs.d/192.168.108.200/etc/containerd/certs.d/192.168.108.200/hosts.toml:server = "http://192.168.108.200"
[host."http://192.168.108.200"]
capabilities = ["pull", "resolve", "push"]
skip_verify = truesystemctl restart containerdcrictl pull 192.168.108.200/library/nginx:latest