adamant-kite-43734
03/07/2024, 1:25 AMcreamy-pencil-82913
03/07/2024, 7:43 AMgreat-action-21630
03/07/2024, 3:58 PMtime="2024-03-07T13:30:23.340519705Z" level=error msg="failed to decode hosts.toml" error="failed to parse TOML: (24, 2): duplicated tables"
The process then tries the default registry, <http://ghcr.io|ghcr.io>
fails and stays on ImagePullBackOff
We understand that duplicate names are not normal but having the process error out is an interesting result.creamy-pencil-82913
03/07/2024, 4:15 PMcreamy-pencil-82913
03/07/2024, 4:16 PMcreamy-pencil-82913
03/07/2024, 4:17 PMgreat-action-21630
03/07/2024, 4:27 PM<http://docker.io|docker.io>:
endpoint:
- "harbor.1.*.*"
- "harbor.2.*.*"
- "<http://harbor.LR|harbor.LR>.*.*"
- "harbor.3.*.*"
- "<http://harbor.LR|harbor.LR>.*.*"
<http://quay.io|quay.io>:
endpoint:
- "harbor.1.*.*"
- "harbor.2.*.*"
- "<http://harbor.LR|harbor.LR>.*.*"
- "harbor.3.*.*"
- "<http://harbor.LR|harbor.LR>.*.*"
<http://k8s.gcr.io|k8s.gcr.io>:
endpoint:
- "harbor.1.*.*"
- "harbor.2.*.*"
- "<http://harbor.LR|harbor.LR>.*.*"
- "harbor.3.*.*"
- "<http://harbor.LR|harbor.LR>.*.*"
We have a server of last resort that gets appended to the end of all the registries as part of our deployment. Some users were adding that same server because they were not seeing it listed as our provision script hadn't run yet.great-action-21630
03/07/2024, 4:29 PMcreamy-pencil-82913
03/07/2024, 4:48 PMgreat-action-21630
03/07/2024, 9:32 PMcreamy-pencil-82913
03/07/2024, 11:47 PM