Note this is copy of original at https://github.com/justingribeiro/chrome-headless The purpose of this copy is to automate the builds and track chrome browser updates with tags according to internal project needs, spiker labs does not claim the rights of this code

Chrome Headless

What was once a container using the experimental build of headless_shell from tip, this container now runs and exposes stable Chrome headless via google-chome --headless.

What's New

1. Pulls from Chrome Stable
2. You can now use the ever-awesome Jessie Frazelle seccomp profile for Chrome. wget https://raw.githubusercontent.com/jfrazelle/dotfiles/master/etc/docker/seccomp/chrome.json -O ~/chrome.json

To run (without seccomp):

docker run -d -p 9222:9222 --cap-add=SYS_ADMIN justinribeiro/chrome-headless

To run a better way (with seccomp):

docker run -d -p 9222:9222 --security-opt seccomp=$HOME/chrome.json justinribeiro/chrome-headless

Using In DevTools

Open Chrome and browse to http://localhost:9222/.

Information on Chrome headless

• Getting Started with Chrome Headless
• Chromium tracker
• Headless Chromium README
• headless-dev mailing list

General Use

docker run -d -p 9222:9222 justinribeiro/chrome-headless

Using In DevTools

Open Chrome and browse to http://localhost:9222/.

#Known issues

Unsafe Scripts

You may have to Load unsafe scripts from the omnibox shield icon to allow connecting to the insecure websocket endpoint ws://localhost:9222:

Red herrings

Depending on the current build, if you run the container interactively you may see things like this on the console:

[0501/162901.033074:WARNING:audio_manager.cc(295)] Multiple instances of AudioManager detected
[0501/162901.033169:WARNING:audio_manager.cc(254)] Multiple instances of AudioManager detected

In most cases, these messages can be safely ignored. They will sometimes change and eventually as things are updated in the source tree, resolved.