[docs-scanner] Contradictory information about Docker Engine 29.0 default storage
维护者通常 1 天内回复
已经有一个关联 PR 被合并了。
- #26166 来自 @jaideepkrishna2008-ui —— 已合并
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 90/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
调研方向
该 issue 指向 content/manuals/engine/storage/drivers/ 目录中的三个特定 Markdown 文件。首先阅读这些文件，以理解关于 Docker Engine 29.0 默认存储的相互矛盾的陈述。修复方法是标准化语言，在 overlayfs-driver.md 中添加“对于全新安装”的限定词并确保一致性。通过检查文档的本地预览来验证更改。
由索引模型根据 Issue 内容生成。
描述
Files:
content/manuals/engine/storage/drivers/_index.mdcontent/manuals/engine/storage/drivers/select-storage-driver.mdcontent/manuals/engine/storage/drivers/overlayfs-driver.md
Issue
Multiple files in the storage drivers section present contradictory information about what Docker Engine 29.0 uses by default. The index file says:
Docker Engine 29.0 and later uses the containerd image store by default for fresh installations, which uses snapshotters instead of classic storage drivers.
But select-storage-driver.md says:
Docker Engine 29.0 and later uses the containerd image store by default for fresh installations.
And overlayfs-driver.md says:
Docker Engine 29.0 and later uses the containerd image store by default. The
overlay2driver is a legacy storage driver that is superseded by theoverlayfscontainerd snapshotter.
The contradiction is: Does Docker Engine 29.0 use containerd image store "by default" (implying always), or only "by default for fresh installations" (implying upgrades use something else)? The index and select-storage-driver pages say "for fresh installations" but overlayfs-driver doesn't include this qualifier.
Why this matters
A reader trying to understand whether their Docker Engine 29.0 installation uses containerd image store or classic storage drivers will get conflicting answers depending on which page they read. This is especially confusing for users who upgraded from an earlier version versus those who did a fresh install.
Suggested fix
Standardize the language across all three files. The most accurate framing appears to be: "Docker Engine 29.0 and later uses the containerd image store by default for fresh installations. If you upgraded from an earlier version, your daemon continues using classic storage drivers unless you migrate."
Apply this consistent language to all three files, particularly updating overlayfs-driver.md to include the "fresh installations" qualifier.
Found by nightly documentation quality scanner
- 主要语言
- Markdown
- 星标
- 4.7k
- 派生
- 8.5k
- 平均合并
- 2 天 21 小时
- 30 天内合并 PR
- 129
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
docker/docs 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
status/triage
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
[docs-scanner] Container proxy table misleadingly presents nested properties as separate parameters可能已有人在做 @dave123981 于 7 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
[docs-scanner] Conflicting WSL version requirements between ECI pages可能已有人在做 @dave123981 于 8 天前认领。 未关闭
难度 1/5 1-3 小时 新手友好度 90/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
相似的 Issue
-
triage
难度 2/5 1-3 小时 新手友好度 76/100
Portkey-AI/gateway#1844 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
XRPLF/xrpl-dev-portal#4000 ·
维护者通常 1 天内回复
-
docs: clarify replacement for outdated Terms of Service URL in readme.md可能已有人在做 @mohitjoshi-hey 今天认领。 未关闭
难度 1/5 1-3 小时 新手友好度 66/100
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
good first issue hacktoberfest pipeline
难度 2/5 1-3 小时 新手友好度 78/100
TanbirRamim/open-source-radar#111 ·
维护者通常 1 天内回复