linuxserver/firefox ¶

Firefox Browser, also known as Mozilla Firefox or simply Firefox, is a free and open-source web browser developed by the Mozilla Foundation and its subsidiary, the Mozilla Corporation. Firefox uses the Gecko layout engine to render web pages, which implements current and anticipated web standards.

Supported Architectures¶

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/firefox:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture	Available	Tag
x86-64	✅	amd64-<version tag>
arm64	✅	arm64v8-<version tag>

Version Tags¶

This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.

Tag	Available	Description
latest	✅	Latest releases using the selkies base
kasm	✅	Latest releases using the kasmvnc base

Application Setup¶

The application can be accessed at:

https://yourhost:3001/

Strict reverse proxies¶

This image uses a self-signed certificate by default. This naturally means the scheme is https. If you are using a reverse proxy which validates certificates, you need to disable this check for the container.

Modern GUI desktop apps may have compatibility issues with the latest Docker syscall restrictions. You can use Docker with the --security-opt seccomp=unconfined setting to allow these syscalls on hosts with older Kernels or libseccomp versions.

Security¶

Warning

This container provides privileged access to the host system. Do not expose it to the Internet unless you have secured it properly.

HTTPS is required for full functionality. Modern browser features such as WebCodecs, used for video and audio, will not function over an insecure HTTP connection.

By default, this container has no authentication. The optional CUSTOM_USER and PASSWORD environment variables enable basic HTTP auth, which is suitable only for securing the container on a trusted local network. For internet exposure, we strongly recommend placing the container behind a reverse proxy, such as SWAG, with a robust authentication mechanism.

The web interface includes a terminal with passwordless sudo access. Any user with access to the GUI can gain root control within the container, install arbitrary software, and probe your local network.

Options in all Selkies-based GUI containers¶

This container is based on Docker Baseimage Selkies, which provides the following environment variables and run configurations to customize its functionality.

Optional Environment Variables¶

Variable	Description
`CUSTOM_PORT`	Internal HTTP port. Defaults to `3000`.
`CUSTOM_HTTPS_PORT`	Internal HTTPS port. Defaults to `3001`.
`CUSTOM_USER`	Username for HTTP Basic Auth. Defaults to `abc`.
`PASSWORD`	Password for HTTP Basic Auth. If unset, authentication is disabled.
`SUBFOLDER`	Application subfolder for reverse proxy configurations. Must include leading and trailing slashes, e.g., `/subfolder/`.
`TITLE`	Page title displayed in the web browser. Defaults to "Selkies".
`START_DOCKER`	If set to `false`, the privileged Docker-in-Docker setup will not start automatically.
`DISABLE_IPV6`	Set to `true` to disable IPv6 support in the container.
`LC_ALL`	Sets the container's locale, e.g., `fr_FR.UTF-8`.
`NO_DECOR`	If set, applications will run without window borders, suitable for PWA usage.
`NO_FULL`	If set, applications will not be automatically fullscreened.
`DISABLE_ZINK`	If set, Zink-related environment variables will not be configured when a video card is detected.
`WATERMARK_PNG`	Full path to a watermark PNG file inside the container, e.g., `/usr/share/selkies/www/icon.png`.
`WATERMARK_LOCATION`	Integer specifying the watermark location: `1` (Top Left), `2` (Top Right), `3` (Bottom Left), `4` (Bottom Right), `5` (Centered), `6` (Animated).

Optional Run Configurations¶

Argument	Description
`--privileged`	Starts a Docker-in-Docker (DinD) environment. For better performance, mount the Docker data directory from the host, e.g., `-v /path/to/docker-data:/var/lib/docker`.
`-v /var/run/docker.sock:/var/run/docker.sock`	Mounts the host's Docker socket to manage host containers from within this container.

Language Support - Internationalization¶

To launch the desktop session in a different language, set the LC_ALL environment variable. For example:

-e LC_ALL=zh_CN.UTF-8 - Chinese
-e LC_ALL=ja_JP.UTF-8 - Japanese
-e LC_ALL=ko_KR.UTF-8 - Korean
-e LC_ALL=ar_AE.UTF-8 - Arabic
-e LC_ALL=ru_RU.UTF-8 - Russian
-e LC_ALL=es_MX.UTF-8 - Spanish (Latin America)
-e LC_ALL=de_DE.UTF-8 - German
-e LC_ALL=fr_FR.UTF-8 - French
-e LC_ALL=nl_NL.UTF-8 - Netherlands
-e LC_ALL=it_IT.UTF-8 - Italian

Nvidia GPU Support¶

Note: Nvidia support is not available for Alpine-based images.

Nvidia GPU support is available by leveraging Zink for OpenGL. When a compatible Nvidia GPU is passed through, it will also be automatically utilized for hardware-accelerated video stream encoding (using the x264enc full-frame profile), significantly reducing CPU load.

Enable Nvidia support with the following runtime flags:

Flag	Description
`--gpus all`	Passes all available host GPUs to the container. This can be filtered to specific GPUs.
`--runtime nvidia`	Specifies the Nvidia runtime, which provides the necessary drivers and tools from the host.

For Docker Compose, you must first configure the Nvidia runtime as the default on the host:

sudo nvidia-ctk runtime configure --runtime=docker --set-as-default
sudo systemctl restart docker

Then, assign the GPU to the service in your compose.yaml:

services:
  firefox:
    image: lscr.io/linuxserver/firefox:latest
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1
              capabilities: [compute,video,graphics,utility]

Application Management¶

There are two methods for installing applications inside the container: PRoot Apps (recommended for persistence) and Native Apps.

PRoot Apps (Persistent)¶

Natively installed packages (e.g., via apt-get install) will not persist if the container is recreated. To retain applications and their settings across container updates, we recommend using proot-apps. These are portable applications installed to the user's persistent $HOME directory.

To install an application, use the command line inside the container:

proot-apps install filezilla

A list of supported applications is available here.

Native Apps (Non-Persistent)¶

You can install packages from the system's native repository using the universal-package-install mod. This method will increase the container's start time and is not persistent. Add the following to your compose.yaml:

  environment:
    - DOCKER_MODS=linuxserver/mods:universal-package-install
    - INSTALL_PACKAGES=libfuse2|git|gdb

Usage¶

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

Info

Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.

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

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

docker cli (click here for more info)¶

docker run -d \
  --name=firefox \
  --security-opt seccomp=unconfined `#optional` \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e FIREFOX_CLI=https://www.linuxserver.io/ `#optional` \
  -p 3000:3000 \
  -p 3001:3001 \
  -v /path/to/firefox/config:/config \
  --shm-size="1gb" \
  --restart unless-stopped \
  lscr.io/linuxserver/firefox: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.

Ports (`-p`)¶

Parameter	Function
`3000:3000`	Firefox desktop gui.
`3001:3001`	Firefox desktop gui HTTPS.

Environment Variables (`-e`)¶

Env	Function
`PUID=1000`	for UserID - see below for explanation
`PGID=1000`	for GroupID - see below for explanation
`TZ=Etc/UTC`	specify a timezone to use, see this list.
`FIREFOX_CLI=https://www.linuxserver.io/`	Specify one or multiple Firefox CLI flags, this string will be passed to the application in full.

Volume Mappings (`-v`)¶

Volume	Function
`/config`	Users home directory in the container, stores local files and settings

Miscellaneous Options¶

Parameter	Function
`--shm-size=`	This is needed for any modern website to function like youtube.
`--security-opt seccomp=unconfined`	For Docker Engine only, many modern gui apps need this to function on older hosts as syscalls are unknown to Docker.

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 firefox /bin/bash
```
To monitor the logs of the container in realtime:
```
docker logs -f firefox
```

Container version number:

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

Image version number:

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

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
```
Single image:
```
docker-compose pull firefox
```

Update containers:

All containers:
```
docker-compose up -d
```
Single container:
```
docker-compose up -d firefox
```

You can also remove the old dangling images:
```
docker image prune
```

Via Docker Run¶

Update the image:

docker pull lscr.io/linuxserver/firefox:latest

Stop the running container:
```
docker stop firefox
```
Delete the container:
```
docker rm firefox
```
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
```

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-firefox.git
cd docker-firefox
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/firefox:latest .

The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static

docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

To help with development, we generate this dependency graph.

Init dependency graph

Versions¶

01.07.25: - Add Kasm branch.
23.06.25: - Rebase to Selkies.
25.09.24: - Rebase to Ubuntu Noble.
23.05.24: - Rebase to Alpine 3.20.
13.02.24: - Add ability to pass CLI args to Firefox.
10.02.24: - Update Readme with new env vars and ingest proper PWA icon.
01.01.24: - Rebase to Alpine 3.19.
13.05.23: - Rebase to Alpine 3.18.
18.03.23: - Rebase to KasmVNC base image.
21.10.22: - Rebase to Alpine 3.16, migrate to s6v3.
23.12.21: - Rebase to Alpine 3.15, stop using ESR.
26.09.21: - Rebase to Alpine 3.14.
19.04.21: - Initial release.

linuxserver/firefox¶