runtime error

Exit code: 1. Reason: g `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules Collecting page data ... Generating static pages (0/5) ... Generating static pages (1/5) Generating static pages (2/5) Generating static pages (3/5) ✓ Generating static pages (5/5) Finalizing page optimization ... Collecting build traces ... Route (app) Size First Load JS ┌ ○ / 5.21 kB 97.4 kB ├ ○ /_not-found 871 B 88 kB ├ ƒ /[roastId] 7.03 kB 99.2 kB └ ƒ /api/og/[slug] 0 B 0 B + First Load JS shared by all 87.1 kB ├ chunks/23-319478583a251706.js 31.6 kB ├ chunks/fd9d1056-2245c12966832080.js 53.6 kB └ other shared chunks (total) 1.89 kB ○ (Static) prerendered as static content ƒ (Dynamic) server-rendered on demand npm notice npm notice New major version of npm available! 10.8.2 -> 11.12.1 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.12.1 npm notice To update run: npm install -g npm@11.12.1 npm notice Prisma schema loaded from prisma/schema.prisma ✔ Generated Prisma Client (v5.19.0) to ./node_modules/@prisma/client in 73ms Start by importing your Prisma Client (See: http://pris.ly/d/importing-client) Tip: Want real-time updates to your database without manual polling? Discover how with Pulse: https://pris.ly/tip-0-pulse Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "dev.db" at "file://data/dev.db" Error: Schema engine error: SQLite database error unable to open database file: //data/dev.db

Container logs: