Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
#20,988 コメント 1 件 リアクション 0 件 担当者 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日 21時間
マージ済み PR(30日)
127

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

docker/docs のほかの issue

docker/docs の issue をすべて見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。