Hi Zach Howell,
Based on your logs and the error "Probe of StartUp failed with status code: 1" plus the message "Target resource doesn't exist," here are focused troubleshooting steps and solutions for running Llama 3 on Azure Container Apps successfully
- The startup probe failing usually means the container app’s readiness/liveness probe can't correctly detect your container is ready.
- ACA uses probes on ports (default 80 or configured port). Make sure your container listens on the correct port and responds with a healthy HTTP status.
- Action: Confirm that your app inside the container is listening on the ACA-configured target port (e.g., 80 or 8000).
- If your app listens on port 8000, configure the container app ingress and probes to use port 8000 explicitly.
Mostly this is a port/probe mismatch or container startup failure. Align container listening port with ACA ingress and probes, allocate the required GPU resources, and validate logs carefully to fix activation errors.
Target resource doesn't exist
This error indicates your application is trying to access a resource (e.g., file, directory, or external service) that is unavailable or misconfigured
Probe Configuration
The startup probe failure suggests ACA is unable to confirm that your app is ready. Ensure the probe is correctly configured.
Reference
az containerapp logs | Microsoft Learn
Enable Application Insights for deeper telemetry and debugging:
Application logging in Azure Container Apps | Microsoft Learn
Kindly let us know if the above helps or you need further assistance on this issue.
Please "Upvote" if the information helped you. This will help us and others in the community as well.
Thanks