By moura
Hey y’all.
I have a very simple python API using Docker. I can build and run it just fine in my local environment but when adding this app to App Platform it starts to build fine but then fails to run.
In my local env I use the following command to run it:
docker run -i -t -p "0.0.0.0:8181:8080" mycontainer:latest
Where can I find more information on how App Platform handles these type of deployments. I have looked at every possible App Platform documentation but could not find it.
Best regards,
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!
Hey! Thank you for the quick reply.
I just double checked, my build goes perfectly but then it fails to run. My Dockerfile specifies the CMD command and my app listens on port 8080 so the default deploy by github should work.
When trying to run I only get this output from the python app:
OpenBLAS WARNING - could not determine the L2 cache size on this system, assuming 256k
I tried to find out if this was the issue but could not find anything relevant.
Best regards
👋 @moura
By default App Platform will try to use buildpacks to automatically detect your app type and then build a container on that.
If you would prefer to use your Dockerfile you can specify this by creating your app with the doctl tool.
Here’s the process to update an existing app:
dockerfile_path property. Here’s more info on the app spec.doctl tool. Here are some install instructions.doctl apps update <app id> ---spec <your app spec> will trigger an update to your appAnd that should get your python api running using the Dockerfile. If you run into specific issues with your App on App Platform please submit a ticket and we can take a look!
Thanks! Happy Hacking!
Hello,
The error “OpenBLAS WARNING - could not determine the L2 cache size on this system, assuming 256k” generally occurs, if the deployment is failing silently with a non-zero exit code error, it could mean that the container is OOMing. There are some cases where that’s not surfaced properly yet in the error code. You could check the memory usage locally in dev and increase the instance size of the app component based on that as an initial size.
We do understand that you have tried to increased the RAM and still noticing this. Are you seeing any slowness or concerns with the APP’s performance in general? Refer to below links, which gives some insights related to this:
https://appspure.net/question/google-app-engine-has-quot-openblas-warning-could-not-determine/ https://www.digitalocean.com/community/questions/app-platform-docker-run-command
Hope this helps!
Cheers, Sri Charan
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.