Puppeteer in Docker: pipe transport vs. WebSocket endpoint for avoiding a publicly reachable debugging port
We run Puppeteer inside Docker containers on a shared host, and the current setup launches Chrome with the default WebSocket transport. My concern is the DevTools endpoint: anyone who can reach the debugging port gets full control of the browser, including cookies and page data, with no authentication. The default binding appears to be loopback-only, but con
docker
puppeteer