Public | Automated Build

Last pushed: 2 months ago
Short Description
Google Chrome via VNC (or via Chrome Remote Desktop - one-time setup req'd via VNC)
Full Description
  • The testing branch for RandR (i.e. "Resize desktop to fit" in CRD client) is merged into master/latest.

Google Chrome via VNC

docker run -p 127.0.0.1:5900:5900 siomiz/chrome

  • Google Chrome, not Chromium, for the ease of Flash plugin management
  • on Xvfb, with FluxBox (no window decorations)
  • served by X11VNC (no password; assuming usage via SSH)

Must agree to Google Chrome ToS to use.

Google Chrome via Chrome Remote Desktop

... so you can use the full Google Chrome with Flash on iPad (with preliminary sound support)!
Much faster than VNC thanks to VP8!

Prerequisite: Create a Profile Volume

You need a VNC client for the initial setup.

  1. docker run -d --name chrome-profile siomiz/chrome (NO password so DO NOT simply use -p 5900:5900 to expose it to the world!)
  2. Connect to the container via VNC. Find the container's IP address by docker inspect -f '{{ .NetworkSettings.IPAddress }}' chrome-profile
  3. Install the "Chrome Remote Desktop" Chrome extension via VNC and activate it, authorize it, and My Computers > Enable Remote Connections, then set a PIN. (Google Account required)
  4. docker stop chrome-profile

(Technically the only config file CRD uses is /home/chrome/.config/chrome-remote-desktop/~host.json which includes OAuth token and private key.)

Usage

docker run -d --volumes-from chrome-profile siomiz/chrome /crdonly (no port needs to be exposed)
/crdonly command will run chrome-remote-desktop in foreground.

Docker ホスト(ヘッドレス可!)で走らせれば、「艦これ」等 Flash ブラウザゲームを iPad/iPhone/Android 等上の Chrome リモート デスクトップ アプリで一応プレイ可能になります。サウンド付き(遅延があります)。
Chrome は英語版ですが、Web ページ用の日本語フォントは含まれています。詳しくはこちら。

Chrome Updates

It is recommended to docker pull siomiz/chrome and restart the container once in a while to update chrome & crd inside (they will not get automatically updated). Optionally you can run docker exec <chrome-container> update to upgrade only google-chrome-stable from outside the container (exit Chrome inside CRD after upgrading).

Docker Pull Command
Owner
siomiz
Source Repository

Comments (9)
olympus78
7 months ago

Hi, very useful image. Please, on the latest image, can we have a bigger resolution like you did for mata? or maybe use environment variables for the resolution size?
Thanks anyway for this great job

mata77
a year ago

Hi siomiz, this is very great and usefull docker :D. Its possible to increase resolution? thanks

siomiz
2 years ago

Hi @nnn21,

I was afraid someone would ask that question...
Anyways, I have added a testing version of this image with :randr tag; it should enable the "Resize Desktop to Fit" option within the CRD client... please try it.
I'm still working on an -e option to set display size.

Thanks!

nnn21
2 years ago

Hi @siomiz,

is it possible to change Chrome Remote Desktop resolution? I tried to edit config.json but there is no effect at all - even after stopping of docker container/service, editing and starting it again.

Thanks!

nernst
2 years ago

Hello @siomiz,

thanks a ton for this comprehensive tutorial. Quite a few things appear to go wrong in this particular setup using putty and vncviewer, the program you suggested worked with only a few tries! And everything works like a charm.

I'm trying to create a setup using Timote and/or Dimote to remote control the webplayers and stream the audio using a chromecast. Maybe I can make it work now ;) Thanks again!

siomiz
2 years ago

Here's a crude English instructions page for the initial setup:
https://github.com/siomiz/chrome/wiki/English

siomiz
2 years ago

Hi @nernst

The VNC server in the chrome-profile step (only required once) is meant to be connected via SSH connection with loopback, because it doesn't have a password set.
You can try -p 5900:5900 or any other port if you're sure the port will not be exposed to the public.

nernst
2 years ago

I might add my procedure: I'm stuck at the chrome-profile step,trying to connect to the 5900 port using the hosts IP adress yields a refused connection.

nernst
2 years ago

I am sure this is a great container considering all the stars and absolutely zero comments with any issues whatsoever.
However, I certainly lack the necessary knowledge with VNC, so please forgive my bold asking:
If I want to set this up (preferably with the Chrome Remote Desktop) on a headless NAS, what do I need to gain VNC access to the container? An additional VNC server on the machine? Or should it just work and something special is messed up in my setup?