truth1984/chromium repository overview

⁠whats new

Enable target features whenever these env variables are present

environment:
  - SOCAT=SOCAT
  - TUNED=TUNED
  - LESSLOG=LESSLOG
  - UA=safari

add SOCAT to enable remote debugging address on 0.0.0.0:13011.

add TUNED to mute audio & remove notifications to save system resources

add LESSLOG to suppress chrome logs

add UA as useragent option: "safari|firefox|chrome|ipad|ioschrome"

fix $CHROME_CLI, now can pass '--var="strings"'

$CHROME_CLI_PLAIN: all other $CLI commands will be ignored, and only this command will be executed

add internationalization with font support (fonts-noto-cjk)

⁠Security !

This Chromium version is outdated. Security vulnerabilities may exist.

Do not use it in production and do not enter any sensitive information.

use -e CHROME_CLI="--disable-gpu --disable-3d-apis --disable-webgl"

⁠versions

u2: 7.12.3, setup: 1.5.0

Manifest v2 enabled & stable-security version:

chromium-common: chromium-common=128.0.6613.84-1~deb12u1

chromium: chromium=128.0.6613.84-1~deb12u1

chromium-l10n: chromium-l10n=128.0.6613.84-1~deb12u1

⁠pull

docker pull truth1984/chromium:v128 (latest, 128.0.6613.84-1~deb12u1)

docker pull truth1984/chromium:v2 (old, 121.0.6167.139-1~deb12u1)

⁠forked from

lscr.io/linuxserver/chromium:latest

⁠Application Setup

The application can be accessed at:

• http://yourhost:3000/⁠
• https://yourhost:3001/⁠

⁠Options in all KasmVNC based GUI containers

This container is based on Docker Baseimage KasmVNC⁠ which means there are additional environment variables and run configurations to enable or disable specific functionality.

⁠Optional environment variables

⁠Optional run configurations

⁠Language Support - Internationalization

The environment variable LC_ALL can be used to start this image in a different language than English simply pass for example to launch the Desktop session in French LC_ALL=fr_FR.UTF-8. Some languages like Chinese, Japanese, or Korean will be missing fonts needed to render properly known as cjk fonts, but others may exist and not be installed. We only ensure fonts for Latin characters are present. Fonts can be installed with a mod on startup.

To install cjk fonts on startup as an example pass the environment variables:

-e DOCKER_MODS=linuxserver/mods:universal-package-install
-e INSTALL_PACKAGES=fonts-noto-cjk
-e LC_ALL=zh_CN.UTF-8

The web interface has the option for "IME Input Mode" in Settings which will allow non english characters to be used from a non en_US keyboard on the client. Once enabled it will perform the same as a local Linux installation set to your locale.

⁠Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

⁠docker-compose (recommended, click here for more info⁠)

---
services:
  chromium:
    image: lscr.io/linuxserver/chromium:latest
    container_name: chromium
    security_opt:
      - seccomp:unconfined #optional
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - CHROME_CLI=https://www.linuxserver.io/ #optional
    volumes:
      - /path/to/config:/config
    ports:
      - 3000:3000
      - 3001:3001
    shm_size: "1gb"
    restart: unless-stopped

⁠docker cli (click here for more info⁠)

docker run -d \
  --name=chromium \
  --security-opt seccomp=unconfined `#optional` \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e CHROME_CLI=https://www.linuxserver.io/ `#optional` \
  -p 3000:3000 \
  -p 3001:3001 \
  -v /path/to/config:/config \
  --shm-size="1gb" \
  --restart unless-stopped \
  lscr.io/linuxserver/chromium:latest

⁠Parameters

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

⁠Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

⁠Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here⁠ before asking for support.

⁠User / Group Identifiers

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

⁠Docker Mods

We publish various Docker Mods⁠ to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

⁠Support Info

• Shell access whilst the container is running:

  docker exec -it chromium /bin/bash
  

  Copy

• To monitor the logs of the container in realtime:

  docker logs -f chromium
  

  Copy

• Container version number:

  docker inspect -f '{{ index .Config.Labels "build_version" }}' chromium
  

  Copy

• Image version number:

  docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/chromium:latest
  

  Copy

⁠Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup⁠ section above to see if it is recommended for the image.

Below are the instructions for updating containers:

⁠Via Docker Compose

• Update images:

  • All images:

    docker-compose pull
    

    Copy

  • Single image:

    docker-compose pull chromium
    

    Copy

• Update containers:

  • All containers:

    docker-compose up -d
    

    Copy

  • Single container:

    docker-compose up -d chromium
    

    Copy

• You can also remove the old dangling images:

  docker image prune
  

  Copy

⁠Via Docker Run

• Update the image:

  docker pull lscr.io/linuxserver/chromium:latest
  

  Copy

• Stop the running container:

  docker stop chromium
  

  Copy

• Delete the container:

  docker rm chromium
  

  Copy

• Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)

• You can also remove the old dangling images:

  docker image prune
  

  Copy

⁠Image Update Notifications - Diun (Docker Image Update Notifier)

tip: We recommend Diun⁠ for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

⁠Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-chromium.git
cd docker-chromium
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/chromium:latest .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset