The value of which can be set in milliseconds, and defaults to 30000, or 30 seconds. This is in place to prevent scripts that don't cleanup properly, or run into errors tha cause them to hang. Connection TimeoutĬonnection timeout is a parameter that sets how long any session can run for. It's best to keep this limit small and grow it over time as it's easy to starve resources when running on restricted hardware. To set this to a different number, say 10, issue your run like so: $ docker run -e 'MAX_CONCURRENT_SESSIONS=10' -p 3000: 3000 -restart always -d -name browserless browserless/chrome Once the limit is reached then queueing begins to take place and requests will wait until more workers are ready. This is, by default, set to 5 when not specified. Since running Chrome can be rather resource intensive you'll probably want to limit the number of concurrent sessions. This should allow you some flexibility in how to run the image. As an example, let's say you want to have it listen port 8080, you would run it like so: $ docker run -p 8080: 3000 -restart always -d -name browserless browserless/chrome You can configure this in docker by using it's port mapping functionality. You can access this information by running the command below: $ docker inspect browserless/chromeīy default browserless listens on port 3000. Chrome informationīrowserless automatically builds labels with each release regarding important information like the current browser version, the version of puppeteer that's supported, and even the debugger version protocol. Below is a description of each parameter, what they mean, and what they default to. You can set parameters such as port, connection-timeout, queueing and more.

The browserless docker container is highly-configurable, and accepts parameters through environment variables when starting. Exposing External Modules for /function.Exposing Built-in Modules for /function.Defining a time to delete workspace files.

Docker for mac network timed out