Report: Not working
Hugging Face Forums [Unofficial]
April 8, 2026
Job failed with exit code: 1. Reason: cache miss: docker-image://docker.io/docker/dockerfile:1@sha256:2780b5c3bab67f1f76c781860de469442999ed1a0d7992a5efdf2cffc0e3d769 cache miss: [runner 3/6] RUN adduser --system --uid 1001 nextjs cache miss: resolve image config for docker-image://docker.io/docker/dockerfile:1 cache miss: [runner 2/6] RUN addgroup --system --gid 1001 nodejs cache miss: [runner 6/6] COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static cache miss: [runner 5/6] COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./ cache miss: [runner 4/6] COPY --from=builder /app/public ./public cache miss: [builder 4/4] RUN if [ -f yarn.lock ]; then yarn run build; elif [ -f package-lock.json ]; then npm run build; elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm run build; else echo “Lockfile not found.” && exit 1; fi && test -f /app/.next/standalone/server.js cache miss: [deps 3/4] COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc* ./ cache miss: [builder 3/4] COPY . . cache miss: [builder 2/4] COPY --from=deps /app/node_modules ./node_modules cache miss: [deps 4/4] RUN if [ -f yarn.lock ]; then yarn --frozen-lockfile; elif [ -f package-lock.json ]; then npm ci; elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm i --frozen-lockfile; else echo “Lockfile not found.” && exit 1; fi {“total”:21,“completed”:16,“user_total”:16,“user_cached”:3,“user_completed”:11,“user_cacheable”:15,“from”:1,“miss”:12,“client_duration_ms”:62631}
Build logs:
===== Build Queued at 2026-04-08 12:41:48 / Commit SHA: 2fe99d9 =====
--> FROM docker.io/library/node:22-alpine@sha256:4d64b49e6c891c8fc821007cb1cdc6c0db7773110ac2c34bf2e6960adef62ed3
DONE 0.0s
--> RUN apk add --no-cache libc6-compat
CACHED
--> WORKDIR /app
CACHED
--> Restoring cache
DONE 1.7s
--> COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc* ./
DONE 0.0s
--> RUN if [ -f yarn.lock ]; then yarn --frozen-lockfile; elif [ -f package-lock.json ]; then npm ci; elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm i --frozen-lockfile; else echo "Lockfile not found." && exit 1; fi
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
added 511 packages, and audited 512 packages in 36s
171 packages are looking for funding
run `npm fund` for details
15 vulnerabilities (2 low, 4 moderate, 8 high, 1 critical)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
npm notice
npm notice New major version of npm available! 10.9.7 -> 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
DONE 37.5s
--> WORKDIR /app
CACHED
--> Restoring cache
DONE 0.2s
--> COPY --from=deps /app/node_modules ./node_modules
DONE 2.7s
--> COPY . .
DONE 0.2s
--> RUN if [ -f yarn.lock ]; then yarn run build; elif [ -f package-lock.json ]; then npm run build; elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm run build; else echo "Lockfile not found." && exit 1; fi && test -f /app/.next/standalone/server.js
> nextjs-gemini-2-0-pdf-structured-data@0.1.0 build
> next build
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 15.2.4
Creating an optimized production build ...
✓ Compiled successfully
Linting and checking validity of types ...
Failed to compile.
./app/api/image/route.ts
3:23 Error: 'HistoryPart' is defined but never used. @typescript-eslint/no-unused-vars
./components/ImageResultDisplay.tsx
60:9 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader 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
93:27 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader 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
./components/ImageUpload.tsx
121:13 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader 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/app/api-reference/config/eslint#disabling-rules
npm notice
npm notice New major version of npm available! 10.9.7 -> 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
--> ERROR: process "/bin/sh -c if [ -f yarn.lock ]; then yarn run build; elif [ -f package-lock.json ]; then npm run build; elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm run build; else echo \"Lockfile not found.\" && exit 1; fi && test -f /app/.next/standalone/server.js" did not complete successfully: exit code: 1
Here: Image Generation & Editing - a Hugging Face Space by Gertie2013
@John6666
Discussion in the ATmosphere