adithya-s-k / adithya-s-k/omniparse
docker pull savatar101/omniparse:0.1 error pulling image configuration
- 主要語言
- Python
- 星號
- 7.9k
- 分支
- 676
- PR 合併指標
- 30 天內沒有已合併 PR
描述
(omniparse-venv) root@ubun:/omniparse# docker pull savatar101/omniparse:0.1
0.1: Pulling from savatar101/omniparse
43f89b94cd7d: Pulling fs layer
5e3b7ee77381: Pulling fs layer
5bd037f007fd: Pulling fs layer
4cda774ad2ec: Waiting
775f22adee62: Waiting
263fc748118f: Waiting
16c36d0187d0: Waiting
e7a56570655c: Waiting
507fc9045cba: Waiting
23b7d8e07c16: Waiting
922ac8fcb889: Waiting
68075f2beca1: Waiting
21f7030b38a3: Waiting
2a8bd6ef46fe: Waiting
9b643c66f2c2: Waiting
bb99debc78b7: Waiting
4f4fb700ef54: Waiting
b209d209d23a: Waiting
93b5d4d94abc: Waiting
error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/df/dfb36453211f8dd962a1608d1fbce2521d41921938ad1824fd352273c89765cb/data?verify=1724153890-3IatWPHo%2F75BucG05jl7ZmBweDA%3D: dial tcp 202.160.130.66:443: i/o timeout
貢獻指南
研究方向
Start by reproducing `docker pull savatar101/omniparse:0.1` and inspect the reported request to production.cloudflare.docker.com, including the `dial tcp ...:443: i/o timeout` failure. There are no repository files or tests mentioned; done would mean determining whether the image configuration can be retrieved successfully or documenting the external connectivity failure.
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- docker
- 領域
- devops, infrastructure
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 15/100