Hi Railway team,

After the May 19 GCP outage, most Postgres services have recovered but mine is still stuck in a continuous crash loop. The volume mounts successfully every time, but the container immediately fails with:

ERROR (catatonit:2): failed to exec pid1: No such file or directory

This appears to be a corrupted container layer where the Postgres binary is missing from the image, even though the volume data is intact.

PROJECT DETAILS:

• Project: selfless-unity
• Project ID: f7ff4408-060f-4c25-9172-171bf7161c7a
• Environment: production
• Service: Postgres
• Service ID: 585ff09e-241d-484d-b628-be05bfc53c74
• Volume: postgres-volume (intact)
• Plan: Hobby

DEPLOY LOG (loops every ~10 seconds):

May 20 2026 06:58:38 Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/9cba2bbd-374b-4664-b6a0-4f3381119f3a/vol_sch06xqrbfn99r8h

May 20 2026 06:59:04 ERROR (catatonit:2): failed to exec pid1: No such file or directory

May 20 2026 06:59:17 Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/9cba2bbd-374b-4664-b6a0-4f3381119f3a/vol_sch06xqrbfn99r8h

May 20 2026 06:59:24 ERROR (catatonit:2): failed to exec pid1: No such file or directory

ATTEMPTS SO FAR:

• 5+ manual restarts (all same error)
• Volume left untouched
• No config changes applied

This is a production database for a client CRM (Villa Somis events). The data on the volume is intact but we cannot reach it because the container won't boot.

Could you redeploy the Postgres container image without touching the volume? Or escalate to an engineer who can rebuild the container layer?

Thanks,

Sam Spedicato