Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
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.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
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.
Source: https://github.com/browserless/browserless/issues/4270
Source: https://github.com/browserless/browserless/issues/4270
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.
Oxylabs: base64 for image downloads, browser_instructions needs render html, tag jobs with client_notes.
Fixes files 'disappearing' from a container when a VOLUME instruction or -v covers the directory COPY populated.