Skip to content

Docker configuration for a ubuntu installation with Chrome, socat and vnc configured by supervisord

License

Notifications You must be signed in to change notification settings

jvitor83/chrome-remote-debug

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Chrome-remote-debug docker with VNC

A Google Chrome docker with VNC and chrome remote debugging enabled. The remote debugging port is exposed with the use of socat. Everything is managed by supervisord.

Running the docker image

make run

The commandline configuration for chrome can be changed by setting environment variables, default.env is loaded when no other file is configured.

Environment variables

  • width (default:1920)
  • height (default:1920)
  • lang (default:en)
  • extra_chrome_args (default:)

Ports

  • 9222: The remote-debugging port of Google Chrome is forwarded by socat
  • 5900: VNC server on port 5900

Extracting the Chrome version number

make version

With this version number a new image can be released

make TAG=60.0.3112.101 builddocker push

Viewing Chrome logs

docker exec -it chrome tail -f /var/log/chrome.log

Important notes

  • The shm-size must be set to a higher value than the default of 64mb because chrome uses this for inter process communications.
  • No password is set for VNC.
  • The chrome sandbox is disabled because the chrome sandbox interferes with the Docker sandbox

Extra info

Chromium command line switches Docker with chrome remote desktop Chrome DevTools Protocol Viewer

About

Docker configuration for a ubuntu installation with Chrome, socat and vnc configured by supervisord

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Dockerfile 56.4%
  • Makefile 34.1%
  • Shell 9.5%