Overview

Deploy Browserless Chromium with a generated API token and the shared-memory setting recommended by Browserless.

Docker image ghcr.io/browserless/chromium:latest
Default port 3000
Deployment type docker image
Recommended resources 1 · 2 GB

How deployment works in DockerCP

This template gives DockerCP the deployment metadata needed to create a service, prepare runtime variables, map persistent storage, expose the internal port, and connect a public domain with SSL when required.

  1. Create or select a project where the service belongs
  2. Review the Docker image, tag, default port, environment variables, and volume mappings
  3. Deploy the service and check logs until the application is healthy
  4. Attach a domain or subdomain when the application must be available publicly
  5. Enable HTTPS and verify the final browser response

Configuration

Environment variables

Variable Default / guidance
TOKEN change_me
CONCURRENT 10
QUEUED 10
TIMEOUT 30000

Persistent volumes

No persistent volume is required by the default template profile

Commands

DockerCP handles deployment from the panel, but understanding the equivalent Docker commands helps users debug services with more confidence. 

docker pull ghcr.io/browserless/chromium:latest
docker ps --filter "name=browserless"

docker logs --tail=100 browserless

DNS and SSL checklist

Step Expected result
Add A or CNAME record The domain points to the DockerCP server or configured target
Attach domain to service The service is reachable through the selected hostname
Enable HTTPS The certificate becomes active and redirect to HTTPS can be enabled

Screenshots

Panel previews for the Browserless template: how deployment, the running service, and its key details look inside DockerCP.

Browserless deployment form inside the DockerCP panel
Headless Chromium browser automation API.
First-boot log output from the deployed container

Troubleshoot

  • Confirm the Docker image and tag exist
  • Confirm the selected internal port matches the application port
  • Confirm required variables such as database URL, app URL, and credentials are set
  • Check service logs after the first deployment
  • Verify DNS before requesting or renewing SSL certificates