popsulfr/chromium-cdp repository overview

⁠Chromium - Chrome Devtools Protocol Docker

https://codeberg.org/popsUlfr/chromium-cdp-docker⁠

Alpine based headless chromium docker image that isn't actually headless.

Runs in a headless wayland session that can be accessed with a VNC client.

Can be gpu accelerated when passing /dev/dri.

⁠Run

podman run --rm \
  --read-only \
  --device /dev/dri \
  --tmpfs /run \
  --tmpfs /tmp \
  -v ./profile:/home/cdp/.config/chromium \
  -v ./cache:/home/cdp/.cache/chromium \
  -p 5900:5900 \
  -p 9222:9222 \
  -e WAYVNC_EXTRA_ARGS="--gpu" \
  -e MESA_SHADER_CACHE_DIR=/tmp \
  docker.io/popsulfr/chromium-cdp:latest

Environment variables:

• SWAY_EXTRA_ARGS=: extra sway arguments
• SWAY_RESOLUTION=1366x768@60Hz: sway virtual screen resolution
• WAYVNC_ADDR=0.0.0.0: wayvnc address to listen on
• WAYVNC_PORT=5900: wayvnc port to listen on
• WAYVNC_EXTRA_ARGS=: extra wayvnc aguments (https://man.archlinux.org/man/wayvnc.1⁠)
• CHROMIUM_REMOTE_DEBUGGING_ADDR=0.0.0.0: chromium remote debugging address to bind to (used by socat)
• CHROMIUM_REMOTE_DEBUGGING_PORT=9222: chromium remote debugging port (used by socat)
• CHROMIUM_REMOTE_DEBUGGING_PORT_INTERNAL=9223: chromium remote debugging port used by the browser
• CHROMIUM_EXTRA_ARGS=: extra chromium arguments (https://peter.sh/experiments/chromium-command-line-switches/⁠)

Folders:

• /home/cdp/.config/chromium: browser profile
• /home/cdp/.cache/chromium: browser cache

⁠VNC

Use a VNC client like TigerVNC to connect to the instance

vncviewer 127.0.0.1