Menu

1 / 2

Chromium + Puppeteer Broke After ASP.NET 8 10 Upgrade — The Hidden Snap Trap in Docker

DEV Community·Pankaj Sharma·6 months ago
#BPAVh3vt
#webdev#ai#chromium#snap#puppeteer
Reading 0:00
15s threshold

We upgraded a service from ASP.NET 8 to 10. No application code changed—but our Puppeteer-based document pipeline completely broke.

The root cause wasn’t .NET. It was a subtle base image change:

Debian → Ubuntu , which replaced a working Chromium install with a non-functional Snap wrapper inside Docker.

The Setup

Our document generation pipeline works like this:

Render HTML using Puppeteer

Use Chromium as the headless browser

Post-process assets with Sharp

Run everything inside a Docker container

This setup worked reliably on ASP.NET 8.

What Changed?

As part of the upgrade:

From: mcr.microsoft.com/dotnet/aspnet:8.0 (Debian-based)

To: mcr.microsoft.com/dotnet/aspnet:10.0 (Ubuntu-based)

At first glance, nothing looked risky.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.