Chrome Headless

To run (without seccomp):

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

To run a better way (with seccomp):

docker run -d -p 9222:9222 --security-opt seccomp=$HOME/chrome.json isholgueras/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 isholgueras/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.

Building and Pushing

To build, ./build.sh <tag>, for example ./build.sh isholgueras/chrome-headless:20211007-chromium

To push, ./build.sh <tag>, for example ./push.sh isholgueras/chrome-headless:20211007-chromium. This will push both amd64 and arm64 images.

Compatibility

This image was updated to chromium to support the new M1 processors. If you prefer keep using the previous chrome version, feel free to use the :chrome tag