Skip to content

Commit 74e6153

Browse files
hub: modify dct deprecation notice (#23869)
<!--Delete sections as needed --> ## Description This PR moves the DCT retirement notice from a callout at the top of the DOI section to a "Troubleshooting failed pulls" subsection at the end. From a user's perspective: - Many users don't have `DOCKER_CONTENT_TRUST=1` set and won't experience any issues. A callout at the top of the page adds unnecessary friction for users just trying to learn about DOI. - Users trying to implement DCT will see notices in DCT docs - Users experiencing pull failures will naturally look for troubleshooting information. Placing this at the end of the section as a dedicated troubleshooting subsection makes it easier to find when they actually need it. - The new structure follows a logical IA flow of learn about DOI → understand how to use them → troubleshoot issues if they occur. ## Related issues or tickets <!-- Related issues, pull requests, or Jira tickets --> ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [ ] Editorial review Signed-off-by: Craig Osterhout <[email protected]>
1 parent 937744b commit 74e6153

File tree

1 file changed

+9
-16
lines changed

1 file changed

+9
-16
lines changed

content/manuals/docker-hub/image-library/trusted-content.md

Lines changed: 9 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -18,22 +18,6 @@ Source Software images.
1818

1919
## Docker Official Images
2020

21-
> [!NOTE]
22-
>
23-
> Docker is retiring Docker Content Trust (DCT) for Docker Official Images
24-
> (DOI). Starting on August 8th, 2025, the oldest of DOI DCT signing
25-
> certificates will begin to expire. You may have already started seeing expiry
26-
> warnings if you use the `docker trust` commands with DOI. These certificates,
27-
> once cached by the Docker client, are not subsequently refreshed, making
28-
> certificate rotation impractical. If you have set the `DOCKER_CONTENT_TRUST`
29-
> environment variable to true (`DOCKER_CONTENT_TRUST=1`), DOI pulls will start to
30-
> fail. The workaround is to unset the `DOCKER_CONTENT_TRUST` environment
31-
> variable. The use of `docker trust inspect` will also start to fail and should
32-
> no longer be used for DOI.
33-
>
34-
> For more details, see
35-
> https://www.docker.com/blog/retiring-docker-content-trust/.
36-
3721
The Docker Official Images are a curated set of Docker repositories hosted on
3822
Docker Hub.
3923

@@ -172,6 +156,15 @@ documentation. Reading through the "How to use this image" and
172156
"Image Variants" sections will help you to understand how to use these
173157
variants.
174158

159+
### Troubleshooting failed pulls
160+
161+
If you're experiencing failed pulls of Docker Official Images, check whether
162+
the `DOCKER_CONTENT_TRUST` environment variable is set to `1`. Starting in
163+
August 2025, Docker Content Trust signing certificates for Docker Official
164+
Images began expiring. To resolve pull failures, unset the `DOCKER_CONTENT_TRUST`
165+
environment variable. For more details, see the
166+
[DCT retirement blog post](https://www.docker.com/blog/retiring-docker-content-trust/).
167+
175168
## Verified Publisher images
176169

177170
The Docker Verified Publisher program provides high-quality images from

0 commit comments

Comments
 (0)