Document how to run Docker container with custom arguments about browserless

[joelgriffith]

Hey there, I’m a tad unclear about the proxy-server (since we don’t have docs on that), which could be making matters worse. There are more elaborate docs here: https://docs.browserless.io/docs/docker.html.

Let me know if that doesn’t cover what you’re trying to achieve

[gajus]

Let me know if that doesn’t cover what you’re trying to achieve

--proxy-server arg should be passed to Chrome when launching it, e.g.

puppeteer/puppeteer#336

Here the docs talk about passing proxy-server parameter via the query parameters, e.g.

https://docs.browserless.io/docs/chrome.html

How does this work? Does Browserless container start a new Chrome instance every time a new connection is made?

[joelgriffith]

How does this work? Does Browserless container start a new Chrome instance every time a new connection is made?

Yup, that's how it functions by default. You can specify it to re-use Chrome instances, but that work is still early in its life-cycle.

[gajus]

Understood. Thank you.

[TAnas0]

@gajus The link https://docs.browserless.io/docs/chrome.html is dead and I stumbled on this issue trying to specify the Websocket port on which Puppeteer listens.

To my understanding, its default value is 0 and means that it will be set randomly high, and I am getting errors about connection being refused to endpoints : 127.0.0.1:<port> where port is random.

Checkout my full description of the problem in this issue.

If this rings any bells, or if you have an alternative link that would be awesome.