docker-chromium:具有Chrome桌面和Web VNC客户端的docker容器，可让您在拥有的任何服务器上运行Ch...

# Docker container for Chromium <img src="https://repository-images.githubusercontent.com/265011647/d609fa80-bad5-11ea-8898-a68379ea5d9f"> This is a Docker container for Chromium. The GUI of the application is accessed through a modern web browser (no installation or configuration needed on client side) or via any VNC client. --- Big thanks to @jlesage. This image is based off https://github.com/jlesage/docker-firefox ___  --- ## Table of Content * [Docker container for Chromium](#docker-container-for-chromium) * [Table of Content](#table-of-content) * [Quick Start](#quick-start) * [Usage](#usage) * [Environment Variables](#environment-variables) * [Data Volumes](#data-volumes) * [Ports](#ports) * [Changing Parameters of a Running Container](#changing-parameters-of-a-running-container) * [Docker Compose File](#docker-compose-file) * [Docker Image Update](#docker-image-update) * [Synology](#synology) * [unRAID](#unraid) * [User/Group IDs](#usergroup-ids) * [Accessing the GUI](#accessing-the-gui) * [Security](#security) * [SSVNC](#ssvnc) * [Certificates](#certificates) * [VNC Password](#vnc-password) * [Reverse Proxy](#reverse-proxy) * [Routing Based on Hostname](#routing-based-on-hostname) * [Routing Based on URL Path](#routing-based-on-url-path) * [Shell Access](#shell-access) * [Increasing Shared Memory Size](#increasing-shared-memory-size) * [Sound Support](#sound-support) * [Setting Chromium Preferences Via Environment Variables](#setting-chromium-preferences-via-environment-variables) * [Troubleshooting](#troubleshooting) * [Crashes](#crashes) * [Support or Contact](#support-or-contact) ## Quick Start **NOTE**: The Docker command provided in this quick start is given as an example and parameters should be adjusted to your need. Launch the Chromium docker container with the following command: ``` docker run -d \ --name=chromium \ -p 5800:5800 \ -v /docker/appdata/chromium:/config:rw \ --shm-size 2g \ overclockedllama/docker-chromium ``` Where: - `/docker/appdata/chromium`: This is where the application stores its configuration, log and any files needing persistency. Browse to `http://your-host-ip:5800` to access the Chromium GUI. ## Usage ``` docker run [-d] \ --name=chromium \ [-e <VARIABLE_NAME>=<VALUE>]... \ [-v <HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS]]... \ [-p <HOST_PORT>:<CONTAINER_PORT>]... \ --shm-size VALUE \ overclockedllama/docker-chromium ``` | Parameter | Description | |-----------|-------------| | -d | Run the container in background. If not set, the container runs in foreground. | | -e | Pass an environment variable to the container. See the [Environment Variables](#environment-variables) section for more details. | | -v | Set a volume mapping (allows to share a folder/file between the host and the container). See the [Data Volumes](#data-volumes) section for more details. | | -p | Set a network port mapping (exposes an internal container port to the host). See the [Ports](#ports) section for more details. | | --shm-size | Set the size of `/dev/shm` to `VALUE`. The format of `VALUE` is `<number><unit>`, where `number` must be greater than `0` and `unit` can be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). **NOTE**: To avoid crashes, it is recommended to set this value to `2g`. | ### Environment Variables To customize some properties of the container, the following environment variables can be passed via the `-e` parameter (one for each variable). Value of this parameter has the format `<VARIABLE_NAME>=<VALUE>`. | Variable | Description | Default | |----------------|----------------------------------------------|---------| |`USER_ID`| ID of the user the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` | |`GROUP_ID`| ID of the group the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` | |`SUP_GROUP_IDS`| Comma-separated list of supplementary group IDs of the application. | (unset) | |`UMASK`| Mask that controls how file permissions are set for newly created files. The value of the mask is in octal notation. By default, this variable is not set and the default umask of `022` is used, meaning that newly created files are readable by everyone, but only writable by the owner. See the following online umask calculator: http://wintelguy.com/umask-calc.pl | (unset) | |`TZ`| [TimeZone] of the container. Timezone can also be set by mapping `/etc/localtime` between the host and the container. | `Etc/UTC` | |`KEEP_APP_RUNNING`| When set to `1`, the application will be automatically restarted if it crashes or if user quits it. | `0` | |`APP_NICENESS`| Priority at which the application should run. A niceness value of -20 is the highest priority and 19 is the lowest priority. By default, niceness is not set, meaning that the default niceness of 0 is used. **NOTE**: A negative niceness (priority increase) requires additional permissions. In this case, the container should be run with the docker option `--cap-add=SYS_NICE`. | (unset) | |`CLEAN_TMP_DIR`| When set to `1`, all files in the `/tmp` directory are delete during the container startup. | `1` | |`DISPLAY_WIDTH`| Width (in pixels) of the application's window. | `1280` | |`DISPLAY_HEIGHT`| Height (in pixels) of the application's window. | `768` | |`SECURE_CONNECTION`| When set to `1`, an encrypted connection is used to access the application's GUI (either via web browser or VNC client). See the [Security](#security) section for more details. | `0` | |`VNC_PASSWORD`| Password needed to connect to the application's GUI. See the [VNC Password](#vnc-password) section for more details. | (unset) | |`X11VNC_EXTRA_OPTS`| Extra options to pass to the x11vnc server running in the Docker container. **WARNING**: For advanced users. Do not use unless you know what you are doing. | (unset) | |`ENABLE_CJK_FONT`| When set to `1`, open source computer font `WenQuanYi Zen Hei` is installed. This font contains a large range of Chinese/Japanese/Korean characters. | `0` | ### Data Volumes The following table describes data volumes used by the container. The mappings are set via the `-v` parameter. Each mapping is specified with the following format: `<HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS]`. | Container path | Permissions | Description | |-----------------|-------------|-------------| |`/config`| rw | This is where the application stores its configuration, log and any files needing persistency. | ### Ports Here is the list of ports used by the container. They can be mapped to the host via the `-p` parameter (one per port mapping). Each mapping is defined in the following format: `<HOST_PORT>:<CONTAINER_PORT>`. The port number inside the container cannot be changed, but you are free to use any port on the host side. | Port | Mapping to host | Description | |------|-----------------|-------------| | 5800 | Mandatory | Port used to access the application's GUI via the web interface. | | 5900 | Optional | Port used to access the application's GUI via the VNC protocol. Optional if no VNC client is used. | ### Changing Parameters of a Running Container As seen, environment variables, volume mappings and port mappings are specified while creating the container. The following steps describe the method used to add, remove or update parameter(s) of an existing container. The generic idea is to destroy and re-create the container: 1. Stop the container (if it is running): ``` docker stop chromium ``` 2. Remove the container: ``` docker rm c