My container-based app fails to deploy without logs or error codes.

If your app using Docker images fails to deploy and the logs are vague or missing, for example you see ERR: container "my-app" in pod "my-app-123456-1234" is waiting to start: trying and failing to pull image with no deploy logs, follow these steps to troubleshoot:

• Make sure the app is working locally, using the same Docker setup.
• Make sure the Dockerfile is built for Linux AMD64 (--platform=linux/amd64).
• Make sure you are not using a duplicate tag, such as latest or debug. Duplicate tags can create conflicts with a cached version when pulling the image. Instead, use a unique tag such as vX.Y.Z or latestv1.
• Update the digest if you’re using one.
• Build the Dockerfile without caching; for example, by running the command docker build --no-cache -t $tag_name.
• Make sure all commands in your Dockerfile are compatible with the Linux build. For example, the COPY command may work locally on an Apple M3 Chip machine, but not Linux AMD64.
• Make sure you set up CMD or ENTRYPOINT properly, ensuring all files have the proper permissions.

Related Topics

Why am I getting an error when trying to forward DigitalOcean Functions to Managed OpenSearch?

Functions does not support forwarding to Managed OpenSearch.

How do I generate my app's SSL certificate?

App Platform automatically generates and issues the SSL certificate during the configuration.

Why am I receiving 520 status codes from my app?

Your app may have crashed while trying to receive an upload or return a response larger than it has been configured to manage.