I'm seeing the same thing, except mine is saying "ERROR (catatonit:2): failed to exec pid1: No such file or directory"

Issue is not resolved on my end. After restarting, PostgreSQL is still crash-looping with the same

docker-entrypoint.sh: not found error. The container image appears to still be broken. Can someone look at my specific

service?

Is the issue on west cost resolved?

please advise. restarting does not work

The connection issue on US West is resolved, Try Redeploy Source Image

not working

please advise asap Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

Starting Container

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cb172101-1c37-4d69-98f6-36c4e64a2d58/vol_awdr12bck2oo9cgo

your agent is saying This is a broken container image — the docker-entrypoint.sh script that PostgreSQL needs to start is missing from the image itself. This is not something you can fix by restarting or reconfiguring the service.

What happened: The pgvector/pgvector:pg18 image you're using appears to be corrupted or incomplete. When the container tries to execute the entrypoint script (/bin/sh -c "unset PGPORT; docker-entrypoint.sh postgres --port=5432"), the script doesn't exist inside the image.

You need to:

Post on your existing support thread with these exact logs so Railway's team understands the image corruption

They can either:

Restore a working version of that image

Help you switch to a different PostgreSQL image source (like the official postgres:18 image instead of pgvector/pgvector)

In the meantime, if you need your database back online quickly, you could try switching the image to postgres:18 (without pgvector extension) as a temporary workaround — but that loses the vector search capability until the proper image is restored.

Head to your open thread and share these crash logs with Railway support. They're the only ones who can fix the image corruption on their end or advise on an alternative image source.

please restore the working image or switch to the official postgres:18 image with pgvector extension

Can you please implement policy so that CVE security patches are not broken when you push out. Please manage patches more carefully with staged rollouts

any estimate on when this issue will be resolved?

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1a5c1058-6be3-44b5-a464-ecd4786621a2/vol_awdr12bck2oo9cgo

Starting Container

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1a5c1058-6be3-44b5-a464-ecd4786621a2/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1a5c1058-6be3-44b5-a464-ecd4786621a2/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1a5c1058-6be3-44b5-a464-ecd4786621a2/vol_awdr12bck2oo9cgo

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1a5c1058-6be3-44b5-a464-ecd4786621a2/vol_awdr12bck2oo9cgo

/bin/sh: 1: docker-entrypoint.sh: not found

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1a5c1058-6be3-44b5-a464-ecd4786621a2/vol_awdr12bck2oo9cgo

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1a5c1058-6be3-44b5-a464-ecd4786621a2/vol_awdr12bck2oo9cgo

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1a5c1058-6be3-44b5-a464-ecd4786621a2/vol_awdr12bck2oo9cgo

I need to know when this issue will get resolved

Restarting won't fix it because it is still using the same image, Redeploy Source Image will pull fresh image from GHCR

Open your Postgres service > Open the Command Palette (Ctrl+K) > Select Redeploy Source Image