18 days ago
Two of my PostgreSQL services have been stuck in a crash loop since 2026-05-20, following incident I23M92U0. Both services show the same symptom: the volume mounts successfully, but the container immediately fails with:
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Restart and redeploy have not resolved either service.
Affected services:
Project/Service ID 9a021f13-56ac-4444-8905-aa43351eafd7, volume vol_4pyafc2u4h32ti32
Project/Service ID e7e3f509-cab8-47ce-bad0-cef0a103eade, volume vol_nihlkv3wlodtxk6f
Since the volumes mount without errors, the data appears intact. Please reprovision the containers against the existing volumes without deleting them.
3 Replies
17 days ago
I'd try redeploying again.
17 days ago
(from the command pallet though)
14 days ago
Dont delete either volume. The catatonit failed to exec pid1 error is usually the container image or startup layer, not the Postgres data files.
For each Postgres service, open the command palette and run Redeploy source image. A normal restart or redeploy can reuse the stale image and keep failing.
If it still loops after that, clone or recreate the Postgres service with the same major version and recover through dump and restore, but keep the original volumes untouched until you have a verified dump. Deleting the volume is the one move that can turn this into real data loss.