2 months ago
I'm successful with running my build on my local system. I adhere to all the space requirements and move my variables over railway when making a deployment. What're your thoughts?
scheduling build on Metal builder "builder-oeyesw"
[snapshot] received sha256:d923cf83fd3b4f0a9f818ef0ebfc70798fa8c86204c6816c0d2bf94c65199f3f md5:4066e92c173a39502e7d85664ca7bd16
receiving snapshot90.2 KB646ms
analyzing snapshot90.2 KB6ms
uploading snapshot90.2 KB21ms
scheduling build on Metal builder "builder-oeyesw"
fetched snapshot sha256:d923cf83fd3b4f0a9f818ef0ebfc70798fa8c86204c6816c0d2bf94c65199f3f (92 kB bytes)
fetching snapshot90.2 KB75ms
unpacking archive400 KB11ms
using build driver railpack-v0.20.0
╭─────────────────╮
│ Railpack 0.20.0 │
╰─────────────────╯
↳ Detected Python
↳ Using pip
Packages
──────────
python │ 3.13.12 │ railpack default (3.13)
Steps
──────────
▸ install
$ python -m venv /app/.venv
$ pip install -r requirements.txt
Deploy
──────────
$ uvicorn main:app --host 0.0.0.0 --port ${PORT:-8000}
load build definition from ./railpack-plan.json
0ms
install mise packages: python
3s
mise python@3.13.12 ✓ installed
python -m venv /app/.venv
4s
copy requirements.txt
535ms
pip install -r requirements.txt
2m 8s
Successfully installed ...
copy / /app
1s
copy /app, /etc/mise/config.toml, /usr/local/bin/mise, /mise/shims, /root/.local/state/mise, /mise/installs cached
190ms
copy /app/.venv
21s
exporting to docker image format
1m 8s
containerimage.config.digest: sha256:6c8ffb37684e3059db4e3ab0dae4c1d16c61d986a2a54e66ea9d3f34214f1f98
containerimage.digest: sha256:49260937c8d8d0343e4cf5c1ce4222698e584e6963beef179139f8af8767f620
containerimage.descriptor: eyJtZWRpYVR5cGUiOiJhcHBsaWNhdGlvbi92bmQub2NpLmltYWdlLm1hbmlmZXN0LnYxK2pzb24iLCJkaWdlc3QiOiJzaGEyNTY6NDkyNjA5MzdjOGQ4ZDAzNDNlNGNmNWMxY2U0MjIyNjk4ZTU4NGU2OTYzYmVlZjE3OTEzOWY4YWY4NzY3ZjYyMCIsInNpemUiOjIwMDksImFubm90YXRpb25zIjp7Im9yZy5vcGVuY29udGFpbmVycy5pbWFnZS5jcmVhdGVkIjoiMjAyNi0wMy0xOVQwNDo1NDozMFoifSwicGxhdGZvcm0iOnsiYXJjaGl0ZWN0dXJlIjoiYW1kNjQiLCJvcyI6ImxpbnV4In19
5 Replies
2 months ago
The build logs you shared show a successful build with no errors. There are no runtime logs available for this deployment, which typically means the service crashed immediately on startup before producing output. Check your deploy logs in the dashboard to see if uvicorn is failing to start, and confirm that the PORT environment variable and any other required variables are set correctly in your service settings.
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Awaiting Railway Response Railway • 2 months ago
Railway
The build logs you shared show a successful build with no errors. There are no runtime logs available for this deployment, which typically means the service crashed immediately on startup before producing output. Check your deploy logs in the dashboard to see if uvicorn is failing to start, and confirm that the `PORT` environment variable and any other required variables are set correctly in your service settings.
2 months ago
please advise
Status changed to Open sam-a • 2 months ago
2 months ago
hey, your build completed fine, can you share your deploy logs?
2 months ago
- Click service, goto setting, in public networking add 8000 as port and update. Then deploy changes. Application will run on url.
Attachments
2 months ago
i didn't have any deploy logs and i had a port set. i just reverted my updates and merged them and somehow it's stable. thank you very much guys. i appreciate your takes
Status changed to Open chandrika • 2 months ago
Status changed to Solved chandrika • 2 months ago