FYI, I sent a message detailing the issue github developer support, who have escalated the issue to the product team with the link to this community post.
I’ll update if I hear back from them.
Update, I figured out my issue:
So nested in the logs ( journalctl ) is the actual issue:
Nov 20 09:42:08 blue-pont dockerd: time="2019-11-20T09:42:08.376878027+11:00" level=warning msg="failed to upload schema2 manifest: unauthorized: This operation would exceed the storage allotment for this account. - falling back to schema1"
Nov 20 09:42:08 blue-pont dockerd: time="2019-11-20T09:42:08.376989057+11:00" level=warning msg="[DEPRECATION NOTICE] registry v2 schema1 support will be removed in an upcoming release. Please contact admins of the docker.pkg.github.com registry NOW to avoid future disruption."
Nov 20 09:42:10 blue-pont dockerd: time="2019-11-20T09:42:10.260794961+11:00" level=error msg="Not continuing with push after error: manifest invalid: Only schema version 2 is supported"
Seems our account is over the storage allocation ( I’m not the certain what this limit is ) and therefore we are no longer able to upload our images.
It is attempting to upload using schema 2 then failing and falling back, docker does not know how to handle the error from the github private repo and is therefor falling back in a reall confusing manner.
So i am not certain if we can delete older packages to free up space or what the limit is.
I used journalctl | grep dockerd (since I aways forget the flags) to get the full logs on Arch Linux, this will be different on OSX (https://docs.docker.com/docker-for-mac/troubleshoot/) or windows (https://docs.docker.com/v17.12/docker-for-windows/troubleshoot/).
But Docker will log the reason it falled back to the version 1 schema in its logs.