runtime error

Exit code: 134. Reason: Generated Prisma Client (v6.6.0) to ./node_modules/@prisma/client in 54ms Start by importing your Prisma Client (See: https://pris.ly/d/importing-client) Tip: Want to react to database changes in your app as they happen? Discover how with Pulse: https://pris.ly/tip-1-pulse npm warn exec The following package was not found and will be installed: [email protected] Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "dev.db" at "file:/data/dev.db" No migration found in prisma/migrations No pending migrations to apply. Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "dev.db" at "file:/data/dev.db" The database is already in sync with the Prisma schema. Running generate... (Use --skip-generate to skip the generators) Warning: You did not specify an output path for your `generator` in schema.prisma. This behavior is deprecated and will no longer be supported in Prisma 7.0.0. To learn more visit https://pris.ly/cli/output-path Running generate... - Prisma Client ✔ Generated Prisma Client (v6.6.0) to ./node_modules/@prisma/client in 37ms > [email protected] start > next start ▲ Next.js 14.2.12 - Local: http://localhost:3000 ✓ Starting... ✓ Ready in 279ms thread '<unnamed>' panicked at query-engine/query-engine-node-api/src/engine.rs:76:45: Failed to deserialize constructor options. This usually happens when the javascript object passed to the constructor is missing properties for the ConstructorOptions fields that must have some value. If you set some of these in javascript through environment variables, make sure there are values for data_model, log_level, and any field that is not Option<T> : Error { status: InvalidArg, reason: "missing field `enableTracing`", maybe_raw: 0x0 } note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace fatal runtime error: failed to initiate panic, error 5 Aborted (core dumped)

Container logs: