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

How do I fix the error "Record is managed by an App on this account, and cannot be deleted"?

Use the app’s Settings tab to remove domains associated with App Platform apps.

Why do I get the error “JavaScript heap out of memory” during deployment?

Increase the heap memory by setting the environment variable NODE_OPTIONS=–max-old-space-size=4096.

How do I fix a "permission denied for schema public" error in my dev database?

Delete the existing dev database and create a new one. Then make sure that the app deployment completes successfully.