I have to say that I am totally puzzled by the #GitHub permission model - if the token has read/write access to content, then why it cannot push #container images to #GHCR?

Back in April, we updated our publish scripts to push new images to the GitHub Container Repository #ghcr instead of #Docker — if you use Docker to deploy #NodeBB, switching is pretty straightforward.

We also detail our reasons for switching.

https://community.nodebb.org/topic/17112/now-publishing-images-to-github-container-registry-registry-migration-faq

#hugops to #ghcr. Also, shipping changes around 5pm on a Friday?

#Docker is killing free team accounts and forcing people to pay for the next tier up ($300usd/mo, not sustainable for many #FOSS projects) or have their teams locked and all OCI images deleted from the 14th May. Dan Manners wrote bash script to help people bulk migrate away from Docker Hub to another registry like #GHCR or your own hosted solution.

Yet another direct blow to the FOSS community by Docker Inc, likely fueled by Mirantis.

https://github.com/danmanners/dockerhub-migration

Is it just me or is `docker manifest inspect` not working anymore for #GitHub Container Registry images? #GHCR

Ugh. #GitHub Container registry is down at the moment. Software development comes to a standstill and there was much weeping and gnashing of teeth...

#ghcr