GitHub container registry - Package not showing on repo

[ghost]

What’s the logic for packages showing up a the repo level?

image406×616 20.4 KB

I have done the following:

• Org level switch to GitHub container registry enabled for private images
• I have a private Docker image built and pushed to GitHub container registry via GitHub actions
• The package shows up at the org level
• I Connected the repository to the container image
• I tried pushing again after they were linked
• The repo packages still doesn’t show anything at bottom right of repo
• There is no packages tab at the repo level

I don’t know that it matters but our org name is Title-Cased but the image repo has to be lower-case.

I also noticed that if I click Publish your first package and then select docker it shows docker.pkg.github.com instead of ghcr.io but maybe that’s just sample docs showing v1 of containers in GitHub packages and not tied into the fact that our org has v2 enabled.

[noahmatisoff]

Hi @ghudik-cas!

The team is working on adding container images pushed to GitHub Container Registry to the repository sidebar. We should have them there soon, it’s not an issue with your organization settings. :slight_smile:

[ghost]

Ahh, good to to know. Thanks @noahmatisoff

[nolim1t]

was wondering why this wasn’t working yet it showed up as successfully built

[clarkbw]

Please check again, this fix should have rolled out now.

[ghost]

I see it now. Thanks!

[airtower-luna]

Nice, thank you!

It seem to work only when logged in though, if I open my test repo in a new browser instance or private window without logging in the “Packages” section say “No packages published”. I can see the package if I click through to packages anyway.

[clarkbw]

Good to know. This logged out experience is because of how we roll out feature flags. Once the flag is removed it will become available to everyone. For now it is only for logged in users.

[airtower-luna]

Ah, that makes sense. Thanks for the explanation! 🙂

[Al-tekreeti]

It looks still not working. I am not able to see the packages even though the build logs indicate a successful pushing to ghcr.io

[andyshinn]

Same. Did this regress? I can push / pull the image. But it is no where in the UI and I cannot manually get to it by name in URL.

[Al-tekreeti]

No, still not working

[justinotero]

I am just packaging up some JS files.
In Github Actions, it says it's successfully built and created a package. However, cannot find it in the Github UI.

I can pull it down via the npm through my CLI.

[tyrads]

I can confirm this is not working again with docker container registry.

[jkovalchik]

Not showing up for me either. Can successfully push/pull the images to/from GCR but they're not showing up under Packages. Interestingly enough, I can see a couple images built a month ago and one built 9 days ago but nothing more recent than that.

[Nassiel]

After all the steps, it still needs to happen for generic packages. Do you have any plans to include this in the future? For instance, I'm pushing an OPA policy in the overall list of packages. It works but is not visible inside the repository despite linking. Thanks @clarkbw :)

[piotrekkr]

Same for me. New repo, build and pushed image as ghcr.io/{repo}:main. Cannot see in GitHub UI but I can pull...

But... I found how to fix it:

• go to https://github.com/orgs/{NAME}/packages (if you are org), or https://github.com/users/{NAME}/packages (normal user)
• find your manually uploaded package and connect with repository

Now I can see package in repository. But to make full use of new package I also needed to add permissions for repositories so they could read/write.

Lesson is that packages seems not related to repository at first creation. You need to actually attach package to repository and add permissions.

Another lesson: THIS IS REALLY POOR UX.

I did not even have a link in UI to package list in my repo. I tried attaching /packages to url and then I had page with links to tutorials on how to create package. Finally I managed to view all packages in my organization and then I actually saw my docker image sent hour ago...

// UPDATE 2024-06-03

Did some testing few weeks ago. Seems like if I use Personal Access Token (PAT) to create a package, it will not be linked to repository and will need to link it manually. If I use GITHUB_TOKEN it will be automatically linked to repository that issues GITHUB_TOKEN. Probably better to use GITHUB_TOKEN with packages: write permissions if it should be assigned to workflow run repository.

[thomasgauvin]

Thanks for providing this @piotrekkr, this resolved my issues

[victorkt]

This worked for me as well, I have to agree it's really poor UX

[NicolasHzGL]

I'm having the same issue, I'm working in a private repo from an organization. I accidentally published it with a typo, instead of widgets-sdk I published widget-sdk. I fixed it and published it again, the package is being published in GitHub packages though because I can install it in other projects and it doesn't let me publish the same version. The UI is not showing it on the organization packages or the repo packages list.
I can only suspect that my typo linked the package to a repo that doesn't exist inside the organization.

[NicolasHzGL]

Hi @clarkbw do you know what could be the issue here?

[Audiosutras]

Running into this issue ☝️ check timestamp

[piotrekkr]

Hi @Audiosutras. I've updated my comment, check it maybe it will help. The gist of it is: using PAT will not link package to repo automatically but using GITHUB_TOKEN will assign package to repo that issued the GITHUB_TOKEN.

[Audiosutras]

Hi @Audiosutras. I've updated my comment, check it maybe it will help. The gist of it is: using PAT will not link package to repo automatically but using GITHUB_TOKEN will assign package to repo that issued the GITHUB_TOKEN.

Thanks for responding. Give me 1-3 days to responds.

[giovannialberto]

Still not working as of 2024.

This is my repo. The package is available here but appears not to be linked to the repository.

[fcuringa]

FYI I also had the same issue, doing the following fixed it for my repository:

1. Go to your personal packages page at https://github.com/{username}?tab=packages (replace username with your actual username)
2. Find the package in the list, click on it
3. Under "Inherited access", check the box "Inherit access from source repository (recommended)".
4. Click on "package settings" and change its visibility to "public".

After that, the package now shows in my repository page as it should.