Container Registry Images not consuming storage

[JeremyGrieshop]

I’ve pushed two private images to GitHub’s container registry, where my Free Org is supposed to have a 0.5 GB limit. The total space, according to docker image ls is 1.7 GB and 1.3 GB. My billing still shows virtually no storage used.

What’s going on? In general, if the image uses layers that GitHub may already have cached, do those count against my storage, or not?

Thanks!

[JeremyGrieshop]

In case anyone else finds this and needs to know the answer - as of 9/1/2021, the Container Registry consumes no storage. This won’t be permanent, though.

All Storage currently consumed in Billing accounts for packages and artifacts created by GitHub Actions.

[wardboumans]

@JeremyGrieshop can you share where this is explained? Im recently noticed this ‘issue’ too. I want to avoid surprises.

[JeremyGrieshop]

Someone from GitHub support replied to me on 9/1/2021:

Thanks for reaching out, I’m sorry for the confusion here! We are not currently charging for storage related to GitHub Package Registry. It was recently moved from beta to generally available, but billing has not been enabled yet. When it is, we will give at least 30 days notice so there will hopefully not be any surprises. Read more here:

GitHub Packages Container registry is generally available | The GitHub Blog

[wardboumans]

Thank you! That clears it up. Guess we have to keep an eye on that notice.

[jricciardi]

Thank you for following up with that message from Support, @JeremyGrieshop! I’ve marked that as the ‘Solution’ here for any future users who find this post.

[sksar]

Any updates as of July 2023?

[DASPRiD]

From what I can see in my usage report, it's still not being counted.

[DFMoller]

My images also are not counting towards package registry storage.