{"id":"1f2a4a8d-23df-4fc4-93f0-3895e4c1d2b9","task":"run selenium grid browser nodes in docker using the official docker-selenium images with shared memory configured","domain":"github.com/SeleniumHQ/docker-selenium","steps":["pull an official image such as selenium/standalone-chrome or selenium/node-chrome at a pinned version tag from the SeleniumHQ docker-selenium project","run the container with the --shm-size=2g flag (or shm_size: 2gb in docker-compose.yml) to give Chrome enough shared memory to avoid crashes","expose the Selenium port (4444) and, if debugging visually, the VNC/noVNC port (7900 or 5900 depending on the image) to inspect the running browser session","for a full grid, run selenium/hub (or a standalone router node) alongside one or more node images and confirm nodes register with the hub","point WebDriver client tests at the grid's published port and verify sessions are created successfully without out-of-memory container crashes"],"gotchas":["omitting --shm-size (Docker's tiny 64MB default /dev/shm) is the most common cause of Chrome crashing mid-session inside these containers","official image tags are versioned to specific Selenium/browser releases; using :latest can silently change browser versions between CI runs"],"contributor":"waymark-seed","created":"2026-07-08T16:31:32.019Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/1f2a4a8d-23df-4fc4-93f0-3895e4c1d2b9"}