ImmichI
Immich•6mo ago
Imanovitz

Manifest unknown

I'm hitting a really puzzling wall trying to get immich-microservices:release (and :latest) pulled from GHCR, and I could really use some fresh eyes on this. My server keeps spitting out an Error response from daemon: manifest unknown.

It's pretty weird because:
  • I can curl -v https://ghcr.io and dig ghcr.io with no issues – connections are good, certificates are valid.
  • Crucially, I can successfully pull ghcr.io/immich-app/immich-server:release! This tells me my docker login ghcr.io (using my PAT with read:packages is working, and general access to GHCR is fine.
I've already run through pretty much all the usual troubleshooting steps on my end:
  • Wiped and re-logged into Docker's GHCR credentials (~/.docker/config.json and /root/.docker/config.json).
  • Restarted the Docker service (systemctl restart docker) multiple times.
  • Ran a full Docker system prune (docker system prune -a -f --volumes) to clear any lingering cache.
  • Even tried to docker rmi the microservices images, but they weren't even locally present.
  • Tried direct docker pull commands for microservices:release and :latest (both still failed with manifest unknown).
  • Portainer also fails to deploy the stack for the same reason.
It feels like my server can talk to GHCR, and it's authenticated, but for some reason, the registry specifically for immich-microservices is telling my Docker daemon it can't find that image's "blueprint" (manifest).

My server setup is Ubuntu 24.04.2 LTS

Has anyone else seen this specific 'manifest unknown' error for immich-microservices recently? Or do you have any ideas what might be going on, since everything else seems to work?

Thanks so much for any help!
Was this page helpful?