test out GitHub registry

[errordeveloper]

It would be nice if PR from external contributors pushed images to contributor's own registry, that way we could avoid having to enable external contributors to push to a shared registry somehow. Seems like GitHub registry should allow this use-case.

[errordeveloper]

What is definitely possible is this: one GitHub user pushes image to their registry (like docker.pkg.github.com/errordeveloper/cilium-image-tools/image-maker:3e2ea4f151593908c362307a1de22e68610d955c-dev). Another user is able to pull it once they logged in (@nebril and I validated this manually). So a registry in a fork of a public is accessible to all logged-in GitHub users.

I am still trying to test a few odd issue I noticed:

• having logged to GitHub registry on my machine, I ran make maker-image PUSH=true REGISTRIES=docker.pkg.github.com/errordeveloper/cilium-image-tools - it hangs forever
• I create a detached fork under errordeveloper/cilium-image-tools-2 and tried the following
  • running from GitHub Action context, first attempt to make iproute2-image resulted in error 403
  • having pushed iproute2 image manually under errordeveloper/cilium-image-tools-2, I was no longer able to push it under errordeveloper/cilium-image-tools, the error I got was blob upload invalid: Package "cilium-iproute2" is already associated with another repository.

I still haven't been able to test it properly, I keep getting all sorts of errors, and base on package <name> is already associated with another repository error, I think it would be hard to make use of GitHub registry for the said purpose, as it appears to detect and prevent duplicate packages.

[errordeveloper]

Overall, I'm not even seeing consistent errors, just no re-running one of the builds I saw invalid content digest in response: invalid checksum digest format instead of 403 that shown previously, I don't think GitHub registry is ready yet.
Also, while I'm seeing 403s, @nebril said that in his experiments Resource not accessible by integration has show up. I'm going to close this for now. One other random errror that I'm not able to reproduce now is 422 Unprocessable Entity.

[errordeveloper]

Looks like GitHub Actions has an outage, I'm going to try and get some more consistent results at least for one or two cases once the service is back.