GHCR private image push partially accepted, attestation stored, final push denied

[MilanDukic]

🏷️ Discussion Type

Bug

Body

Hello GitHub Community,

I'm experiencing a problem publishing a Docker image to GitHub Container Registry (GHCR).

Account: MilanDukic
Package: ghcr.io/milandukic/globalpaw365-staging-sql-client
Tag: phase4ai
Failure time: November 9, 2026, 06:36:13–06:36:18 UTC

What happened

I attempted to push a verified Linux/amd64 Docker image to GHCR.

• Several image blobs were successfully uploaded.
• GHCR accepted one untagged provenance attestation.
• Docker then returned error from registry: denied.
• The push exited with code 1.
• The package exists with Private visibility.
• No tagged executable image was published.
• I made exactly one push attempt, with no retries.

Expected digests

OCI index:
sha256:885d74528efa045dd3f041de4e944ed0803cdcbbdd53bf38372f488abd36e3dc

Linux/amd64 manifest:
sha256:aa29a09499ca70da2663b922426ac9301bf98e15dfac26fd1672d11d9402eb8d

Accepted untagged attestation:
sha256:d40b7552cadce569719b133c67ccbdc815a447399999d686a38f2d4a84dc72eb

Authentication

• Classic Personal Access Token with write:packages.
• Successful docker login ghcr.io.
• Publishing account has Admin access to the package.
• Docker Desktop credential helper is configured.

The exact denied registry operation is unknown.

Questions

1. Has anyone experienced GHCR accepting image layers and an attestation but denying the final image publication?
2. Could this involve GitHub's OCI manifest/attestation handling?
3. What additional safe, read-only diagnostics could identify the cause?
4. Is there a recommended correction that does not require deleting the existing private package?

I would appreciate guidance before retrying the push.

Thank you!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐