Self-host Firefox with Levelrail

A private Firefox browser running on your server and streamed to a web page.

  • Memory1 GiB
  • Archarm64
  • Services1

How to self-host Firefox

  1. Pull the images

    One image is pulled on your server.

    Show images
    • jlesage/firefox:latest
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 5800.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Firefox requirements

Memory
About 1 GiB
Architectures
amd64 image published, arm64 image published
Ports
5800
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 5800 on the host, so open them in the VPS firewall only if you want that.
  • Review. Image is not pinned to a version tag, so a redeploy can pull different code (jlesage/firefox:latest).

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Firefox. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Firefox docs page.

Deploy Firefox your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Firefox from the CLI

levelrail-cli templates deploy firefox-browser --name my-firefox-browser

Deploy Firefox with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/firefox-browser/deploy

Firefox configuration

Firefox services

ServiceImagePortsVolumes
firefox jlesage/firefox:latest 5800 firefox_config -> /config

Firefox environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
5800
Volumes
1 named mount: firefox_config -> /config

Firefox FAQ

How much memory does Firefox need?

The catalog lists about 1 GiB of memory for Firefox.

Does Firefox run on arm64?

For Firefox, an arm64 image is published; amd64 is image published.

Does Firefox need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Firefox use?

Firefox listens on port 5800 inside the stack.

Where does Firefox keep its data?

In a named volume: firefox_config mounted at /config.

Can I deploy Firefox on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Firefox, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image jlesage/firefox:latest is what you deploy there.

levelrail-cli templates deploy firefox-browser --name my-firefox-browser