Skip to content

docs: remove duplicate DCT deprecation notice in content trust overview #25156

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dvdksn merged 1 commit into from
May 25, 2026
+0 −11
Merged

docs: remove duplicate DCT deprecation notice in content trust overview #25156

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions content/manuals/engine/security/trust/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,17 +124,6 @@ set. For more information, see the [Notary GitHub repository](https://github.com
A prerequisite for signing an image is a Docker Registry with a Notary server (such as Docker Hub) attached.
Refer to [Deploying Notary](/engine/security/trust/deploying_notary/) for instructions.

> [!NOTE]
>
> Docker is retiring DCT for Docker Official Images
> (DOI). You should start planning to transition to a different image signing
> and verification solution (like [Sigstore](https://www.sigstore.dev/) or
> [Notation](https://github.com/notaryproject/notation#readme)). Timelines for the
> complete deprecation of DCT are being finalized and will be published soon.
>
> For more information, see [Retiring Docker Content Trust](https://www.docker.com/blog/retiring-docker-content-trust/).


To sign a Docker Image you will need a delegation key pair. These keys
can be generated locally using `$ docker trust key generate` or generated
by a certificate authority.
Expand Down