Browser Infrastructure Browser
Infrastructure & Scale/Advanced

Scaling & Orchestration

Running concurrent browser pools inside containerized environments (Docker, Kubernetes).

Dependency Path
Requires:
Used By:
Environment Target
Compatibility: Chrome >= 110, nodriver >= 1.0
Last Reviewed: 2026-07-18
Recipes: 9 (1 cookbook / 8 playbook)

Why It Matters

Running concurrent browser pools inside containerized environments (Docker, Kubernetes).Also known as: concurrency, browser pool, docker configurations.

scalingdockerorchestrationperformance

Operating a cluster of browser instances requires scaling memory bounds, preventing memory leak loops, running inside head-deprived Linux environments, and managing proxy load balancers.

Execution Plan

  1. Shared Memory Access: Configure /dev/shm in Docker containers to avoid tab crashes from low memory limits.
  2. Zombie Process Cleanup: Use tiny-inits (tini) in Docker entries to clean up orphaned Chrome processes.
  3. Queue Balancing: Maintain a pool manager that routes tasks to warm, idling browser targets.

Example Recipes

+3 more recipes in the knowledge base

Book Coverage

Python Browser Automation Cookbook
1 recipe covering this concept
Browser Automation Playbook
8 recipes covering this concept

Next Steps