Railway's own Postrgres addon's failing
fen747
PROOP

a month ago

Hello world, I've got an emergency

Using Railway's provided postgres addon on my app (https://railway.com/project/4ad6fa2d-b5d8-4bf5-8f47-7cbb499f2ba4/service/eba184fe-fe97-47d5-b898-6becd2a1fe55?environmentId=eac01fcd-107e-44dc-9d0f-b2cb1b6b80fa)

Add on : https://railway.com/project/4ad6fa2d-b5d8-4bf5-8f47-7cbb499f2ba4/service/dbee4230-88b0-43b2-aa9c-d5096c6ec25f/database?environmentId=eac01fcd-107e-44dc-9d0f-b2cb1b6b80fa

Deployment ID: 1d09273f-b10f-4f49-8aa1-dac8a6e2732b

Service: Postgres (EU West region)

Issue: Template image ghcr.io/railwayapp-templates/postgres-ssl:18 has broken Dockerfile—missing package-lock.json for npm ci

Impact: Production database crashed days ago, still can't restart

I didn't do anything specific to this addon, it's just the standard on proposed by railway, just took its db URL to use it in my app. Worked at first.

Solved

1 Replies

Railway
BOT

a month ago

The Postgres service deploys from a pre-built container image in the registry, not by building the Dockerfile each time. Open your Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image" to re-pull a fresh copy of that pre-built image. A normal redeploy from the 3-dot menu will not re-pull the image and will not fix this. Your volume data remains intact through this process.


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved fen747 about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...