Pulling the image without credentials. Image: reg.xxx.lan:5000/xxx/pause:3.9

version info and cmdline

# cri-dockerd --version
cri-dockerd 0.3.4 (e88b1605)
# systemctl cat cri-dockerd
...
ExecStart=/usr/local/bin/cri-dockerd \
    --container-runtime-endpoint unix:///var/run/cri-dockerd.sock \
    --network-plugin=cni \
    --cni-bin-dir=/data/kube/bin/ \
    --pod-infra-container-image=reg.xxx.lan:5000/xxx/pause:3.9

cri-dockerd cannot pull reg.xxx.lan:5000/xxx/pause:3.9

9月 05 15:43:00 xxx-PC cri-dockerd[27149]: time="2023-09-05T15:43:00+08:00" level=info msg="Pulling the image without credentials. Image: reg.xxx.lan:5000/xxx/pause:3.9"
9月 05 15:43:01 xxx-PC cri-dockerd[27149]: time="2023-09-05T15:43:01+08:00" level=info msg="Pulling the image without credentials. Image: reg.xxx.lan:5000/xxx/pause:3.9"
9月 05 15:43:02 xxx-PC cri-dockerd[27149]: time="2023-09-05T15:43:02+08:00" level=info msg="Pulling the image without credentials. Image: reg.xxx.lan:5000/xxx/pause:3.9"
9月 05 15:43:05 xxx-PC cri-dockerd[27149]: time="2023-09-05T15:43:05+08:00" level=info msg="Pulling the image without credentials. Image: reg.xxx.lan:5000/xxx/pause:3.9"
9月 05 15:43:05 xxx-PC cri-dockerd[27149]: time="2023-09-05T15:43:05+08:00" level=info msg="Pulling the image without credentials. Image: reg.xxx.lan:5000/xxx/pause:3.9"
.....

how to used credentials for pod-infra-container-image

The report only identifies the cri-dockerd service command line and repeated image-pull logs; no source file or test is named. Start by tracing how cri-dockerd handles credentials for the configured pod-infra-container-image and determine the supported credential path. Done means the private image can be pulled with documented credentials, or the limitation is clearly documented.