Github Container registry ( packages not appearing in webinterface

Hello Github community,

I wanted to try out the new Github Container registry that was announced today.

With the Docker CLI I could successfully log in (using a personal access token) and push an image:

$ docker login
Username: my-github-username
Password *******************
$ docker pull hello-world:latest
$ docker tag hello-world:latest
$ docker push

This seems to have worked. The container image seems to be available at the registry:

docker manifest inspect
	"schemaVersion": 2,

But it doesn’t seem to be public:

$ docker logout
docker manifest inspect
denied: unauthenticated: User cannot be authenticated with the token provided.

I was now looking to modify the permissions. According to the docs I should be able to see the newly pushed container image on my github profile under packages.

But I’m only getting the default “getting started” screen there (as if I had zero packages):


Am I doing anything wrong? Any help would be appreciated. Thanks in advance!

1 Like

:wave: Thanks for trying it out!

Packages are initially published as private. You should be able to find them by looking for it under your user account

Now that we’ve launched publicly we’ll be wiring up support for associated containers to show up along side the repository. Until then you’ll need to go to your org or user account view to find them.

You can also go directly to by name

Here’s the URL scheme:


thanks for the direct URL @clarkbw , unfortunately the package (container image) doesn’t appear there either (also changing visibility = all is the same):

But I definitely have a container image on that I can pull with Docker (once I’m logged in with a personal access token):

$ docker pull
latest: Pulling from my-github-username/hello-world
Digest: sha256:90659bf80b44ce6be8234e6ff90a1ac34acbeb826903b02cfa0da11c82cbc042
Status: Downloaded newer image for

Any ideas? Thanks!

1 Like

quick addition: I can indeed access this URL directly:

So manually assembling this URL with the container name seems to resolve my issue. Thanks for that @clarkbw !

(However, I can’t access this page from anywhere else and even this page incorrectly states that there are 0 packages).



Excellent! The Edit Package drop down will have options for changing the package visibility and deleting versions. The switch to public should allow for authentication free access.

The other connections from the repo and search are being hooked up right now. Hang tight and we’ll have those addressed soon.


same here :frowning:
any updates on that?
That makes migration from to painful for us.
give us at least some API call example

Having the same issue here. I can access the package by directly accessing the container URL but it doesn’t show up in my private packages neither in its related repository.

Also note that accessing it through :

This work :

This triggers a 500 error :

Edit: It seems to show up after the first time the image was pulled. The 500 error is also gone. Looks like there is some kind of lazy loading happening where the package is not associated to the repository or account until it’s pulled from docker.

1 Like

Wow, thanks for posting this. I didn’t realize this issue was still a thing. My team will likely be switching to GitHub for container images next year. This is good to know.