Build Errors FAQ
We understand that encountering errors can be frustrating, but fear not! We try to give helpful error messages whenever something goes wrong or unexpected happens.
In this part, we'll guide you through the various error messages you may come across and help you understand what they mean and what you can do to resolve them.
A slightly more advanced Banana user. If you haven't deployed a model on Banana or read through the getting started guide, we highly recommend doing that first and consulting this section if case it's needed.
Also, if you're a long time Banana user, note that these errors are only on Banana V2. V1 errors are not covered here.
- Verify on a local development environment your build succeeds before pushing
- Click into the model in the dashboard, open the "Logs" tab, and view the build logs there. Be patient, build logs can take up to 20s to be loaded.
Currently, all Potassium apps on Banana are required to have the base Docker image as
pytorch/pytorch:1.11.0-cuda11.3-cudnn8-runtime. We understand that this might be restricting for some of you and hopefully we'll be able to support more base images in the near future.Banana healthchecks your build twice:
- 1.Once with your built base image
- 2.then again once we hook our python runtime into it.
Common causes for "second healthcheck failed" are:
- Potassium app not found within your source. Follow this interface to ensure our runtime discovers your potassium app.