Description:
I'm experiencing persistent Docker image pull failures when trying to deploy Postiz to my Zeabur project. The deployment fails at the image pull stage with authorization/access denied errors.
Project Details:
Project ID: 696e8e3c04512dd9764fc592
Project Name: Postiz
Region: Silicon Valley, United States (sjc1)
Services Affected:
Service ID (old attempt): 696e8e5a2952d01a4bd04e2e
Service ID (new attempt): 696eb0c22952d01a4bd05380
Error Messages:
First attempt with ghcr.io/neondatabase/postiz:latest:
Failed to pull image "ghcr.io/neondatabase/postiz:latest": failed to pull and unpack image "ghcr.io/neondatabase/postiz:latest": failed to resolve reference "ghcr.io/neondatabase/postiz:latest": failed to authorize: failed to fetch anonymous token: unexpected status: 403 Forbidden
Second attempt with gitroom/postiz:latest:
Failed to pull image "gitroom/postiz:latest": failed to pull and unpack image "docker.io/gitroom/postiz:latest": failed to resolve reference "docker.io/gitroom/postiz:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Template deployment attempt also resulted in image pull failures.
What I've Tried:
Deployed using Docker image ghcr.io/neondatabase/postiz:latest
Deployed using Docker image gitroom/postiz:latest
Deployed using the official Postiz template (code: CWN6IC)
All attempts result in image pull authorization/access errors
Environment:
PostgreSQL and Redis services are running successfully in the same project
Only the Postiz service is failing to pull its image
The issue persists across multiple deployment attempts
Request:
Could you please investigate why Docker image pulls are failing with authorization errors? This appears to be an infrastructure-level issue rather than a configuration problem on my end.