[docs-scanner] DCT retirement notice missing from trust documentation pages

オープン
  • 何か問題がありますか？
#26,286 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

  • #26287 @nielskaspers による — マージされずにクローズ

評価

難易度
1/5
見積もり時間
1〜3時間
初心者へのやさしさ
35/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
停滞
技術スタック
markdown
領域
documentation

調査の方向性

Read the existing retirement warning in content/manuals/engine/security/trust/_index.md and compare it with the five listed trust pages. Add the specified notice, shutdown date, and retirement-documentation link to each page, then verify all five render with the warning at the top. A linked open pull request is already present, so check its status before starting.

索引モデルが issue の本文から書いたものです。

説明

area/engine area/security status/confirmed

Files:

  • content/manuals/engine/security/trust/deploying_notary.md
  • content/manuals/engine/security/trust/trust_automation.md
  • content/manuals/engine/security/trust/trust_delegation.md
  • content/manuals/engine/security/trust/trust_key_mng.md
  • content/manuals/engine/security/trust/trust_sandbox.md
Issue

The main index page (_index.md) contains a prominent warning that Docker Content Trust is being retired:

Docker Content Trust (DCT) is being retired. The Notary v1 service at
notary.docker.io will shut down on December 8, 2026.

However, all five other pages in this directory provide detailed how-to instructions for using DCT with no mention of this retirement or deprecation. These pages read as if DCT is a current, fully-supported feature:

  • deploying_notary.md - "The easiest way to deploy Notary Server is by using Docker Compose"
  • trust_automation.md - "It is very common for Docker Content Trust to be built into existing automation systems"
  • trust_delegation.md - "Delegations in Docker Content Trust (DCT) allow you to control who can and cannot sign an image tag"
  • trust_key_mng.md - "Trust for an image tag is managed through the use of keys"
  • trust_sandbox.md - "This page explains how to set up and use a sandbox for experimenting with trust"
Why this matters

A reader who navigates directly to any of these five pages (via search, link, or navigation) will follow detailed instructions to set up and use DCT without knowing it's being retired. They may invest significant time configuring DCT only to discover later that:

  1. The service is shutting down in December 2026
  2. They need to migrate to an alternative solution
  3. The feature they just learned is deprecated

This is particularly problematic for the automation and delegation pages, which describe integration patterns that would require significant investment.

Suggested fix

Add a deprecation notice at the top of each of these five pages, similar to the warning in _index.md. The notice should:

  1. State that DCT is being retired
  2. Mention the December 8, 2026 shutdown date
  3. Link to the retirement documentation at /manuals/retired.md#docker-content-trust-dct

Example:

> [!WARNING]
>
> Docker Content Trust (DCT) is being retired. The Notary v1 service at
> `notary.docker.io` will shut down on December 8, 2026. For more information, see
> [Docker Content Trust (DCT)](/manuals/retired.md#docker-content-trust-dct).

Found by nightly documentation quality scanner

主要言語
Markdown
スター
4.7k
フォーク
8.5k
平均マージ
2日 11時間
マージ済み PR（30日）
135

環境構築

はじめの一歩

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

docker/docs のほかの issue

docker/docs の issue をすべて見る

似ている issue

Documentation の issue をもっと見る

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

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