Your service is deploying from the supabase/postgres Docker image, which skips the build step entirely, so no build logs are expected. The supabase/postgres image is very large (multiple GB), and pulling it can take a significant amount of time. Deploy logs will only appear once the image pull completes and the container starts. Both the "postgres" and "easygoing-kindness" services in your Caristeo ERP project are currently in DEPLOYING status, which is consistent with a large image pull in progress.

Now the build failed and I im still without seeing the logs.

The IA diagnostic is:

Yes, this is a Railway infrastructure issue, not a problem with your service configuration.

Here's what happened:

Your deployment failed at the container creation stage due to a transient platform disruption

A second service in your environment (also using the same postgres image) failed at the exact same time with the identical error

Both services got stuck retrying for ~26 minutes before timing out

The underlying issue resolved itself — the postgres service automatically triggered a new deployment that succeeded

What to do:

Redeploy your service. The infrastructure issue has passed, so it should work now.

railway deploy

If it fails again with the same error, contact Railway support — they can investigate further. But based on the diagnosis, a simple redeploy should resolve it.

failed to pull image: docker.io/supabase/postgres:latest: not found