I can push images to container registry but I cannot pull them, MANIFEST_UNKNOWN error

[kevinbyrd98]

Select Topic Area

Question: How do i resolve manifest unknown error so I can pull docker images from github container registry.

Body

I am trying to utilize github container registry on my Github Enterprise 3.10.2 server, I have an action that successfully tags and pushes the image, and I can view it under the packages of the repository, but attempts to pull the image results in this error:

Error response from daemon: unknown: {"errors":[{"code":"MANIFEST_UNKNOWN","message":"Docker image reference selfservice:sha256:fc3c521817030e003465308ac87ad76511e65cd69c9f0229553d6bb9ec033848 not found under repo \"iss\""}]}

I have an access token with read/write access to packages

I have subdomain isolation enabled

[dev-ugurkontel]

Possible Reasons:

Subdomain Isolation: If subdomain isolation is enabled in GitHub Enterprise, by default different subdomains cannot access each other's packages.
Authorization Problem: The access token you are using may lack the necessary authorizations (read/write).
Solution Steps:

Subdomain Isolation Settings:

If you need to pull images between different subdomains, go to GitHub Enterprise admin settings.
Open the "Packages" tab and check the "Subdomain Isolation" setting.
Set permissions for the subdomain you want to pull the image from.
Check Access Token:

Make sure that the access token you use has "packages: read" and "packages: write" permissions.
If it does not have the required authorizations, create a new token and add these authorizations.
Additional info:

If the problem persists, you can obtain more detailed information by examining the log files.
You can review the sections on "Packages" and "Subdomain Isolation" in the GitHub Enterprise documentation.
Note:

If these steps do not resolve the issue, you can contact GitHub Enterprise support for further assistance.

[grandmas-favorite]

Nice @dev-ugurkontel! Exactly what I would have suggested 😄

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬