Repository navigation
Using a remote chromium via a ws_url requires a local chromium binary #554
Description
I'm probably missing a key reason that this is required.
But why is that I have to have a locally installed chromium binary if I'm operating a remote chrome via ws_url?
That was surprising at first when I saw it.
But perhaps that should not be surprising at all!
Curious at a minimum to know the answer to this question.
But perhaps there could be a documentation addition that grows out of this.
Activity
route commentedon Feb 9, 2026
Where is it required? It should not be
route commentedon Oct 18, 2026
Confirming this works without any local browser: Ferrum's CI now runs its whole suite on an arm64 runner that has no Chrome installed, against our
ghcr.io/rubycdp/chromiumimage overurl:.With #651,
ws_url:won't even make an HTTP request anymore, browser details come over CDP. https://github.com/rubycdp/ferrum/blob/main/docker/DESIGN.md