6 hours ago
builder
RUN npm ci --ignore-scripts
1s
Build Failed: build daemon returned an error < failed to solve: process "/bin/sh -c set -eux; echo "deb http://deb.debian.org/debian bullseye-backports main" >> /etc/apt/sources.list.d/backports.list; apt-get update; apt-get -o Acquire::Retries=3 install -y --no-install-recommends ca-certificates wget gnupg2 fonts-liberation libatk1.0-0 libatk-bridge2.0-0 libcups2 libdrm2 libgbm1 libgtk-3-0 libnss3 libx11-xcb1 libxcomposite1 libxdamage1 libxrandr2 libxss1 libasound2 libpangocairo-1.0-0 libxkbcommon0 || (echo "Retrying apt install after short sleep..." && sleep 5 && apt-get update && apt-get -o Acquire::Retries=3 --fix-missing install -y --no-install-recommends ca-certificates wget gnupg2 fonts-liberation libatk1.0-0 libatk-bridge2.0-0 libcups2 libdrm2 libgbm1 libgtk-3-0 libnss3 libx11-xcb1 libxcomposite1 libxdamage1 libxrandr2 libxss1 libasound2 libpangocairo-1.0-0 libxkbcommon0); apt-get -o Acquire::Retries=3 -y -t bullseye-backports install --no-install-recommends chromium || (echo "Retrying backports chromium install..." && sleep 5 && apt-get update && apt-get -o Acquire::Retries=3 -y -t bullseye-backports install --no-install-recommends chromium); rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code:
2 Replies
6 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 6 hours ago
6 hours ago
Build › Build image
(00:13)
Failed to build an image. Please check the build logs for more details.
Diagnosis › Infrastructure Error
Run automatically
This build failed because Debian's package mirror returned a 404 error while installing Chromium's system libraries in the Dockerfile, not because of your code changes. The commit only modified UI text in a React component, and the Dockerfile's apt-get install step is unchanged, so this points to a temporary problem fetching packages from the upstream Debian mirror. Try redeploying, and reach out to support if it keeps failing.
6 hours ago
This build failure isn't a temporary mirror glitch Debian 11 "bullseye" has moved out of its standard support window, and Debian relocates EOL releases (including their backports) from deb.debian.org to archive.debian.org. Once that switch happens, apt-get update against deb.debian.org/debian plus bullseye-backports starts returning 404s for the Release/Packages files, which surfaces as the install failing after retries — even though the Dockerfile itself never changed. That's why it broke with no code changes and why the previously-stable branch fails too: it's the base image's package index going stale, not the app.
Fix options:
1. Point apt at the archive (fastest patch, stays on bullseye)
Add this before your apt-get update step:
RUN echo "deb http://archive.debian.org/debian bullseye main" > /etc/apt/sources.list && \
echo "deb http://archive.debian.org/debian-security bullseye-security main" >> /etc/apt/sources.list && \
echo "deb http://archive.debian.org/debian bullseye-backports main" >> /etc/apt/sources.list.d/backports.list && \
echo 'Acquire::Check-Valid-Until "false";' > /etc/apt/apt.conf.d/99no-check-valid-until2. Upgrade the base image (recommended)
If your FROM line uses a bullseye-based image, bump it to bookworm (Debian 12). Bookworm has a recent Chromium in main, so you can drop the backports step entirely:
RUN apt-get update && apt-get install -y --no-install-recommends chromium ...3. Skip apt for Chromium entirely
If this is for Puppeteer/Playwright, use their own browser install (npx playwright install --with-deps, or Puppeteer's bundled download) instead of apt/backports — avoids Debian lifecycle issues altogether.
Could you share the FROM line of your Dockerfile? That'll confirm which base image you're on and which fix applies cleanly.