Question
Django app build packs error have suddenly disappeared
- Posted on October 11, 2023
- Building on DigitalOceanDjangoPython
Asked by tsenovilla
Hi all!
I’m trying to deploy a Django app to DO, but I’m getting a weird response. Yesterday I deployed the same app and everything was OK, but today I’m not able to do it again (I had to fix a small issue, so I need to deploy iy again). Here you can find the logs I’m getting:
[2023-10-11 10:09:34] ╭──────────── buildpack detection ───────────╼
[2023-10-11 10:09:34] │ › using Ubuntu 22.04 stack
[2023-10-11 10:09:36] │ ✘ could not detect app files that match known buildpacks.
[2023-10-11 10:09:36] │ please ensure that the files required by the desired language's buildpack exist in the repo.
[2023-10-11 10:09:36] │ review the buildpack documentation for more info: https://do.co/apps-buildpacks
[]
I’ve been investigating a bit and I found out that this problem may happen when the repo does not contain a requirements.txt/setup.py/Pipfile, which is not my case. I’ve changed some lines in my python code, but I’ve neither installed any additional package nor changed the requirements.txt file. In addition, I’ve read that DigitalOcean’s default Python version has recently changed, but I think this cannot be the reason as I have a runtime.txt in my repo specifying the version I need (3.11.3). Thus, I can’t understand why the file is not being detected from one day to the next
I’ve also notified that the Python build pack no longer appears in the Build Phase section of my project’s settings.
Any idea of how can I solve this? Thank you so much in advance!
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.
Featured on Community
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hey @tsenovilla,
We deeply apologize for the inconvenience you’ve experienced following the transition to Ubuntu 22. Our intent behind updating the default stack was to provide a more enhanced and up-to-date platform for our users. However, we understand that the transition has not been smooth for everyone.
If 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.
It looks like that a few more people are experiencing the same issue with other buildpacks as well:
I’ve escalated this internally already, but what you could do in the meantime is to reach out to the DigitalOcean support team who will be more than happy to assist you with your issue in the meantime:
Best,
- Bobby.
Did you find out why this happens? 8.02.2024 and I still have the same problem