R
Railway3y ago
demo

Sudden build failure

Updated a README and pushed and was surprised that my build is now failing.
================
Using Buildpacks
================
20: Pulling from heroku/buildpacks

Digest: sha256:ec85cb9658066b31a4d5d9a0f6816bfa112ff626f93afaead872812226eb6f2b
Status: Image is up to date for heroku/buildpacks:20

20-cnb: Pulling from heroku/heroku

Digest: sha256:c233084a9a068c6526928956bfe2445ed1a7d05cc696cec089ce87c40fd99893
Status: Image is up to date for heroku/heroku:20-cnb

Previous image with name "us-west1-docker.pkg.dev/railway-infra/railway-docker-users/project/d604ae57-452b-43f3-9f81-fb085605c65a/service/c9766d5a-0506-4b50-966f-0e36e1345105:f93dbef6-1e8e-4ec9-a164-d1fbc69ed99d" not found
===> DETECTING

heroku/python 0.0.0
heroku/procfile 1.0.2
===> RESTORING
===> BUILDING

----> No Python version was specified. Using the buildpack default: python-3.10.7
To use a different version, see: https://devcenter.heroku.com/articles/python-runtimes

! Requested runtime 'python-3.10.7' is not available for this stack (heroku-20).
! For supported versions, see: https://devcenter.heroku.com/articles/python-support

ERROR: failed to build: exit status 1

ERROR: failed to build: executing lifecycle: failed with status code: 51

================
Using Buildpacks
================
20: Pulling from heroku/buildpacks

Digest: sha256:ec85cb9658066b31a4d5d9a0f6816bfa112ff626f93afaead872812226eb6f2b
Status: Image is up to date for heroku/buildpacks:20

20-cnb: Pulling from heroku/heroku

Digest: sha256:c233084a9a068c6526928956bfe2445ed1a7d05cc696cec089ce87c40fd99893
Status: Image is up to date for heroku/heroku:20-cnb

Previous image with name "us-west1-docker.pkg.dev/railway-infra/railway-docker-users/project/d604ae57-452b-43f3-9f81-fb085605c65a/service/c9766d5a-0506-4b50-966f-0e36e1345105:f93dbef6-1e8e-4ec9-a164-d1fbc69ed99d" not found
===> DETECTING

heroku/python 0.0.0
heroku/procfile 1.0.2
===> RESTORING
===> BUILDING

----> No Python version was specified. Using the buildpack default: python-3.10.7
To use a different version, see: https://devcenter.heroku.com/articles/python-runtimes

! Requested runtime 'python-3.10.7' is not available for this stack (heroku-20).
! For supported versions, see: https://devcenter.heroku.com/articles/python-support

ERROR: failed to build: exit status 1

ERROR: failed to build: executing lifecycle: failed with status code: 51

6 Replies
demo
demoOP3y ago
looks like service is still live though another push and healthy again. Resolved.
Faraz
Faraz3y ago
Looks like you're on Heroku buildpacks btw. Any reason you haven't moved to Nixpacks yet?
demo
demoOP3y ago
Moved from heroku to railway and wanted to keep my initial workflow at the time - especially knowing that I could likely also shift to other services like fly.io if I determined I needed their feature set. But no worries, I'm having a good time on railway and have no plan of moving off platform. I'll get around to moving to nix packs probably when railway gives me a pop-up saying my heroku config will start failing
Unknown User
Unknown User3y ago
Message Not Public
Sign In & Join Server To View
demo
demoOP3y ago
upgraded to nixpacks successfully was indeed painless
Unknown User
Unknown User3y ago
Message Not Public
Sign In & Join Server To View
Want results from more Discord servers?
Add your server