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

Ouverte
  • Quelque chose ne va pas ?
#26,286 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

  • #26287 par @nielskaspers — fermée sans fusion

Évaluation

Difficulté
1/5
Temps estimé
1-3 heures
Accessibilité débutants
35/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
À l'abandon
Stack technique
markdown
Domaine
documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Markdown
Étoiles
4.7k
Forks
8.5k
Merge moyen
2 j 11 h
PR mergées (30 j)
135

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de docker/docs

Toutes les issues de docker/docs

Issues similaires

Plus d'issues Documentation

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.