Skip to content
Deployment stops before container starts
Anonymous
OP

a month ago

kompas-status-1791514276685.jpg

Solved

1 Reply

Railway
BOT

a month ago

These redeploys are failing because the environment has grown too large to apply, not because of a manual stop or anything in the build. The kompas-kamtibmas service ships its application as base64 bundles split across numbered variables (the KOMPAS150_BUNDLE_* and APP_BUNDLE_* sets), and its start command decodes and runs them at boot. Keeping code in variables isn't supported. Once the payload gets big enough, deploys and staged changes stop going through, and retrying, restaging, or adding more chunks only adds to the payload.

To fix it, deploy the application code from a connected repo, or build and publish an image and deploy that. Keep large files on a volume or in object storage. Then delete the bundle variables and swap the start command for a short command that runs the deployed files. Variables should only hold configuration and secrets.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...