Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Multi-platform builds and containerd image store sections are ambiguous, overlap, and missing info

未关闭
#20,988 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@dvdksn 已经在做这个了。

开始于 2024年9月24日。

评估

这个 Issue 还没有评估数据。

描述

area/build area/engine kind/enhancement lifecycle/frozen
Is this a docs issue?
  • My issue is about the documentation content or website
Type of issue

Information is incorrect

Description

The "Multi-platform builds" section is confusing, and has some parts that are ambiguous;

  • It outlines prerequisites
  • But due to how they are presented, are easy to be interpreted as "you must enable the containerd image store" AND "create a custom builder"

That's incorrect, because creating a custom builder is only needed if the containerd image-store is NOT enabled. There's information in the first paragraphs, but the "make sure that your builder and Docker Engine support multi-platform build" makes it easy to interpret it as "I need to configure both to make this work".

Screenshot 2024-09-24 at 19 50 54 Screenshot 2024-09-24 at 19 56 01

There's duplicate content as well;

Missing information

QEMU as prerequisite

As an important use of the containerd image-store is to facilitate multi-platform builds, we should also consider;

Storage drivers

Given that the containerd image-store uses different drivers than graphdrivers, we may want to mention this, and perhaps include an example that specifies the default driver to use, e.g.;

{
  "features": {
    "containerd-snapshotter": true
  },
  "storage-driver": "overlayfs"
}
  • Perhaps the storage-drivers section should also include information about snapshotters
  • Mention which pages do NOT apply to the containerd image-store
Location

https://docs.docker.com/build/building/multi-platform/#prerequisites

Suggestion

See above

主要语言
Markdown
星标
4.7k
派生
8.5k
平均合并
1 天 22 小时
30 天内合并 PR
128

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

docker/docs 的其他 Issue

查看 docker/docs 的全部 Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。