[docs-scanner] DCT retirement notice missing from trust documentation pages
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
- #26287 de @nielskaspers — cerrado sin fusionar
Evaluación
- Dificultad
- 1/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Estancado
- Stack tecnológico
- markdown
- Área
- documentation
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Files:
content/manuals/engine/security/trust/deploying_notary.mdcontent/manuals/engine/security/trust/trust_automation.mdcontent/manuals/engine/security/trust/trust_delegation.mdcontent/manuals/engine/security/trust/trust_key_mng.mdcontent/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.iowill 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:
- The service is shutting down in December 2026
- They need to migrate to an alternative solution
- 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:
- State that DCT is being retired
- Mention the December 8, 2026 shutdown date
- 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
- Lenguaje dominante
- Markdown
- Estrellas
- 4.7k
- Forks
- 8.5k
- Merge medio
- 2 d 11 h
- PR fusionados (30 d)
- 135
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de docker/docs
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
Los mantenedores suelen responder en 1 día
-
[docs-scanner] S3 and Azure Blob cache backends marked as unreleased but have complete documentationAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
status/triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
Los mantenedores suelen responder en 1 día
-
[docs-scanner] Confusing explanation of approval-required outcome vs permit in MCP policyPosiblemente ocupada @dave123981 la tomó hace 3 días. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
Todos los issues de docker/docs
Issues similares
-
Contribute FeedbackAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 67/100
MicrosoftDocs/WSL#2654 ·
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 85/100
hibernate/hibernate-reactive#4485 ·
Los mantenedores suelen responder en 1 día
-
vuln:LOW
Dificultad 1/5 Menos de una hora Aptitud para principiantes 63/100
curl/curl-www#679 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
mxschmitt/awesome-playwright#285 ·
Los mantenedores suelen responder en 19 días
-
area/access-management Frontend onboarding candidate :handshake:
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Altinn/altinn-auth#4941 ·
Los mantenedores suelen responder en 1 día