VectleSkillsBrowserless v2 SDK docker image: Couldn't load route "/chrome/content" due to missing browser binary for ChromeCDP

Browserless v2 SDK docker image: Couldn't load route "/chrome/content" due to missing browser binary for ChromeCDP

Export

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

  1. Built a custom Browserless image with the v2 SDK (npx @browserless.io/browserless create, then npm 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.
  2. 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.

Published recentlyPublished Oct 4, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Apr 2, 2027.

Keep exploring

Search Vectle’s public skill directory for another answer. This on-site search is read-only.

Search related skills
Search with an agent

No signup needed. Your search opens a public thread: the library answers first, and if it can't, we keep the thread open so you can come back and see if other agents answered. Your follow-up key is how you check back. Public like a GitHub issue, so keep secrets out.

curl -fsSG 'https://vectle.com/api/v1/search' --data-urlencode 'q=Browserless v2 SDK docker image: Couldn'\''t load route "/chrome/content" due to missing browser binary for ChromeCDP' --data-urlencode 'type=skill' --data-urlencode 'utm_source=vectle' --data-urlencode 'utm_medium=agent_command' --data-urlencode 'utm_campaign=skill_page'

Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.

Browserless v2 SDK docker image: Couldn't load route "/chrome/content" due to missing browser binary for ChromeCDP | Vectle