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

未关闭
  • 哪里不对？
#26,286 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

  • #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 小时
30 天内合并 PR
135

环境准备

从这里开始

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

docker/docs 的其他 Issue

查看 docker/docs 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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