Question
App platform build phase of service errors with Job Terminated error
- Posted on January 6, 2023
- Building on DigitalOceanDigitalOcean App Platform
Asked by webdever
I’m building a web service and I get this error on the build phase:
Build Error: Job Terminated
Component Issues
ws failed to build
And these are the last logs before the error:
[2023-01-06 16:11:35] │ Running custom build command: yarn nx run models:generate && yarn nx build ws --prod
[2023-01-06 16:11:36] │ yarn run v1.22.19
[2023-01-06 16:11:36] │ $ /workspace/node_modules/.bin/nx run models:generate
[2023-01-06 16:11:39] │
[2023-01-06 16:11:39] │ > nx run models:generate
[2023-01-06 16:11:39] │
[2023-01-06 16:11:41] │ > Nx Prisma Generating Client
[2023-01-06 16:11:41] │ [command]/tmp/yarn--1673021496365-0.10943475819062609/yarn prisma generate --schema=libs/models/src/prisma/schema.prisma
$ /workspace/node_modules/.bin/prisma generate --schema=libs/models/src/prisma/schema.prisma
[2023-01-06 16:11:44] │ Environment variables loaded from .env
[2023-01-06 16:11:44] │ Prisma schema loaded from libs/models/src/prisma/schema.prisma
[2023-01-06 16:11:46] │ ✔ Generated Prisma Client (4.8.0 | library) to ./node_modules/@prisma/client in 1.41s
[2023-01-06 16:11:46] │ You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
[2023-01-06 16:11:46] │ ```
[2023-01-06 16:11:46] │ import { PrismaClient } from '@prisma/client'
[2023-01-06 16:11:46] │ const prisma = new PrismaClient()
[2023-01-06 16:11:46] │ ```
[2023-01-06 16:11:46] │
[2023-01-06 16:11:46] │
[2023-01-06 16:11:46] │
[2023-01-06 16:11:46] │ > NX Successfully ran target generate for project models
[2023-01-06 16:11:46] │
[2023-01-06 16:11:46] │
[2023-01-06 16:11:46] │ View logs and investigate cache misses at https://nx.app/runs/KXmK7Hc6aV
[2023-01-06 16:11:46] │
[2023-01-06 16:11:47] │ Done in 10.72s.
[2023-01-06 16:11:47] │ yarn run v1.22.19
[2023-01-06 16:11:47] │ $ /workspace/node_modules/.bin/nx build ws --prod
[2023-01-06 16:11:47] │
[2023-01-06 16:11:47] │ > nx run ws:build:production
[2023-01-06 16:11:47] │
[2023-01-06 16:12:13] │ chunk (runtime: main) main.js (main) 21.1 KiB (javascript) 937 bytes (runtime) [entry] [rendered]
[2023-01-06 16:12:13] │ webpack compiled successfully (4d135dcbae6414bf)
[2023-01-06 16:12:14] │
[2023-01-06 16:12:14] │
[2023-01-06 16:12:14] │
[2023-01-06 16:12:14] │ > NX Successfully ran target build for project ws
[2023-01-06 16:12:14] │
[2023-01-06 16:12:14] │
[2023-01-06 16:12:14] │ View logs and investigate cache misses at https://nx.app/runs/dd7tvTpFka
[2023-01-06 16:12:14] │
[2023-01-06 16:12:14] │ Done in 27.01s.
[2023-01-06 16:12:15] ╰───────────────────────────────────╼
[2023-01-06 16:12:15]
[2023-01-06 16:12:15] ╭──────────── app upload ───────────╼
[2023-01-06 16:12:15] │ › uploading app container image to DOCR
[2023-01-06 16:12:17] │ Adding layer 'heroku/nodejs-engine:nodejs'
[2023-01-06 16:12:19] │ Adding layer 'heroku/nodejs-engine:yarn'
[]
As you can see, there’s almost no way to debug this just from the logs.
Also, it’s worth noting that https://docs.digitalocean.com/products/app-platform/reference/error-codes/ doesn’t even list the Job Terminated error code.
Do you guys have any idea how to debug this or how to fix it?
Thanks
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!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Get started for free
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
New accounts only. By submitting your email you agree to our Privacy Policy.
same error here with django-react app. cant resolve that.
I had same issue with a React app. I did 2 things to resolve:
I forced a Rebuild and Deploy. This led to an error saying that permissions to my repo on Github were not enabled. (That didn’t make sense either, because the failed build was automatically launched from a push to Github). I removed the permissions for the DigitalOcean Github app, re-enabled, and did a “Rebuild and Deploy” again.
After the second “Rebuild and Deploy”, I got an error that still had no logs available, but this time it indicated “component failure”. This led me to manually attempt a
yarn buildfrom my local development environment in an attempt to recreate and/or debug any build issues that may be hidden in the app platform. I found a few eslint configuration issues as well as a few deprecated packages. Apparently, these were no problem in my dev environment nor were they an issue with previous app platform deployments. Since all of us experienced this around the same time, my guess is maybe something changed in a buildpack recently that made deployments more particular about errors or caused failures for build warnings that were previously ignored.After addressing all build issues locally, my most recent push to Github resulted in a successful automatic build and deploy.
+1 we’re experiencing the same error. No more info in the logs. It’s as if DO decided to terminate the build for some reason.