What to check first
Use a scratch repository to test who can publish, then check how consumers identify the expected image digest.
Choose a KeySigner setup
| Setup guide | What it does and what to keep available |
|---|---|
| Test a Docker Hub browser sign-in code → | Use KeySigner as the second factor when signing in to a Docker Hub account in a browser. You need KeySigner on iPhone or Mac with Sign-in codes. Keep available The Docker Hub recovery code and an active browser session until the new code works. |
| Check an approved multi-platform image → | Verify that Docker Hub serves the exact multi-platform image your release owners approved. You need Docker Buildx, jq, a SHA-256 tool and a KeySigner test release workflow. Keep available The approved index digest and any independent publisher verification your release policy requires. |
What it covers
Protecting a publisher account does not prove the image content or make a tag immutable.
Troubleshooting
Can the build pull the image but not publish a tag?
Inspect the access token's write permission and confirm that its user can push to the exact namespace and repository.
Recover access to Docker Hub →
Check Docker Hub status for reports on Docker Hub’s hosted registry.
Documentation and support
Docker Hub documentation
Review publishing token permissions
Enable two-factor authentication in Docker
Inspect a multi-platform image and its digest