Browserless v2 SDK docker image: Couldn't load route "/chrome/content" due to missing browser binary for ChromeCDP
Shows how to fix browserless v2 SDK docker image: Couldn't load route "/chrome/content" due to missing browser binary for ChromeCDP. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For "Couldn't load route "/chrome/content?(/)" due to missing browser binary for "ChromeCDP"": upgrade to @browserless.io/browserless 2.30.0 or newer and rebuild your image against the matching browser image (ghcr.io/browserless/chromium) on linux/arm64. Built a custom Browserless image with the v2 SDK (npx @browserless.io/browserless create, then npm run docker).
Couldn't load route "/chrome/content?(/)" due to missing browser binary for "ChromeCDP"Steps
- Built a custom Browserless image with the v2 SDK (
npx @browserless.io/browserless create, thennpm run docker). On ARM64 the container starts but every Chrome route fails with:Couldn't load route "/chrome/content?(/)" due to missing browser binary for "ChromeCDP". The maintainer found the SDK's Dockerfile was pulling browser binaries via npx, which installed the latest stable package instead of the binaries matching the SDK version, so the expected ChromeCDP binary wasnt there. - Fixed in the Browserless v2 SDK. Upgrade to @browserless.io/browserless 2.30.0 or newer and rebuild your image against the matching browser image (ghcr.io/browserless/chromium) on linux/arm64. The original reporter confirmed the missing-binary error is gone on 2.30.0, and the maintainer closed the issue as solved from their testing.
Expected: Fixed in the Browserless v2 SDK.
When to use
You are seeing this: On ARM64 the container starts but every Chrome route fails with: Couldn't load route "/chrome/content?(/)" due to missing browser binary for "ChromeCDP". Use this skill when you run into "Browserless v2 SDK docker image: Couldn't load route "/chrome/content" due to missing browser binary for ChromeCDP".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: 2.30.0. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.