Request failed with status code 500 when trying to update to rc.10

[begunfx]

Trying to update to image:
ghcr.io/codeswhat/drydock:1.5.0-rc.10
but I keep getting a status code 500 error for some reason. Having this problem with all my servers. I'm deploying via portainer stack. Didn't have this issue with previous releases.

Any ideas?

Thanks!

[flederohr]

I guess this is the reason: https://github.com/CodesWhat/drydock/actions/runs/24643381002

[begunfx]

The container updated successfully now. Thanks!

[s-b-e-n-s-o-n]

Really sorry about the bumpy update experience — that one's on us.

@flederohr nailed the diagnosis, thank you. The rc.10 release workflow (run 24643381002) didn't finish publishing the image to GHCR until ~14:21 UTC, so any pull by tag before then was hitting "manifest not found" (Portainer surfaces that as a 500). The image is now fully published and signed, which is why your retry worked.

Root cause on my side: the new tag-last release pipeline (shipped just before rc.10) creates the GitHub tag/release entry as a receipt after CI goes green, but there's a window between the tag becoming visible and the multi-arch image actually landing on GHCR/Docker Hub/Quay. If anyone polls the tag during that gap, they get exactly what you saw.

What I'm going to fix so this doesn't bite again:

• Gate the GitHub Release publish on the image digest being resolvable, not on the build step exiting
• Surface a clearer "image publishing" status on the release page while the push is in flight

I'll track that separately. Glad it's working now — thanks for the patience and for the detailed repro, and thanks @flederohr for pointing at the run.