I use DigitalOcean to host a Django project, I’ve been using them for about 18 months with no major issues, today I tried to deploy a new build and am being told:
could not detect app files that match known buildpacks.
Before that I was getting:
Requested runtime 'python-3.8.3' is not available for this stack (heroku-22).
Which I corrected by changing my runtime.txt file
Can anyone help me with this?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hello,
Quick update for anyone who comes across this thread in the future. We deeply apologize for the inconvenience you’ve experienced following the transition to Ubuntu 22.
What you could try out first is to do a force redeployment of your app and this should fix the problem in most cases. If you are however still seeing the issue, and your application is experiencing issues with the new build packs available in Ubuntu 22, it is likely due to older versions of the software you’re running. We’ve noticed this has affected a number of our users. Here are your immediate options:
Downgrade to Ubuntu 18: By modifying your app spec, you can revert to using Ubuntu 18, which should restore compatibility for your application. You can follow the instructions here: How to Change Stack.
Upgrade Your Software: If you’re keen on benefiting from the updates in Ubuntu 22, consider upgrading your software versions. Afterwards, ensure you select the correct build pack supported in the Ubuntu 22 stack. The guide on how to do this can be found here: How to Upgrade Buildpacks.
For those who have pinned older build packs from Ubuntu 18, it’s crucial to plan a switch to the ones available in Ubuntu 22 for optimal functionality.
We genuinely appreciate your patience during this transition. Our team is actively monitoring feedback and is here to assist you every step of the way. If you need further assistance or have more questions, please don’t hesitate to reach out.
Feel free to reply to this thread here in case that you have any further questions!
Best,
Bobby
I fixed this temporarily by changing my entire app’s Python version to 3.11.4. It’s the only version I’ve managed to get to work with heroku-22 and heroku-18. Others like 3.10.13 or 3.11.6 do not work.
This hack is an unacceptable fix. Changing the Python version is a luxury others - or myself and my own app - may not have in the future. I’ve already gotten a few irreproducible errors from a worker service running DjangoQ which weren’t there before.
I may have fixed the situation, but if DO does not clarify what happened, I will leave the platform.
I’m also getting the same error for go