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

Offen
#26,286 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

  • #26287 von @nielskaspers — ohne Merge geschlossen

Bewertung

Schwierigkeit
1/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
35/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
markdown
Bereich
documentation

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
Markdown
Sterne
4.7k
Forks
8.5k
Ø Merge
2 T. 11 Std.
Gemergte PRs (30 T.)
135

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus docker/docs

Alle Issues in docker/docs

Ähnliche Issues

Weitere Issues zu Documentation

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.