Browser

Firefox, runningon the machine itself

Mozilla's browser on a Void Linux desktop of your own.The profile lives on the volume, so it is there next time.

Firefox 155.02 cores · 4 GBOpens in a browser tab

hub://firefox

$ dxflow workflow create --identity firefox hub://firefox --start --link

01Pick a machinecores, memory and a rate per hour

02Create the workflowpulled from the hub, once

03Run it, then stopstopped when the work is done

The application

Gecko,not another Blink

Mozilla's browser and its own engine, already installed.

A second engine

Gecko and not Blink, so a page can be checked against the second renderer.

It browses from there

Pages load over the machine's network, so it reaches what the machine can.

The profile persists

History, bookmarks and signed-in sessions stay on the volume between runs.

How you run it

Every defaultis one override away

The session reads its settings from the environment, so you set them on the start line.

VNC_PASSWORDWhat the tab asks for. It ships as dxflow, and everyone reading this knows that.

PANEL and TASKBARBoth hidden, so the browser has the whole screen. Show either one to get the desktop back.

AUDIOOff here. Turn it on and what plays in the page plays in your tab too.

start it your way

$ dxflow workflow start firefox --override env.app.VNC_PASSWORD=something-long

$ dxflow workflow start firefox --override env.app.AUDIO=on --link

The session

One tab of yours,a whole browser inside

Streamed to your browser, with Firefox already maximized.

6082Browserin the tab, at /vnc.html

5901VNCin a native client

/volumeStoragethe profile and its bookmarks

Open it from anywhereStart with --link and the session comes back on an HTTPS address.

Set a password firstVNC_PASSWORD defaults to dxflow, and everyone can read this page.

Good to know

A browser that runswhere the data is

Firefox here is not a second copy of the one on your laptop. It sits next to the machine's network.

It browses from the cloud

Requests leave from the machine's address. Reach an internal service, or a site that should not see where you actually are.

The profile belongs on the volume

Keep downloads and the profile under /volume and the next start opens with your sessions still signed in.

It is still a browser

Tabs cost memory here exactly as they do anywhere. Pick the machine for how many you actually keep open.

The image

Pulled once,then it stays

Firefox arrives as one image. This is what comes down the first time, and what the disk should have free for it.

388Mamd64compressed, the way the registry counts it

382Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/firefox:latestPublished from the hub, pulled on the first start and kept for the ones after it.

Either architectureamd64 and arm64 are both published, and the machine pulls the one it runs.

What it asks for

What it wants,and what it needs

The definition asks for 2 cores and 4 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.

2 cores · 4 GBAsks forwhat the definition writes down

2 cores · 2 GBRuns onthe least the image comes up on

Not neededGPUit works on the cores alone

The ask is not the floorThe definition writes down what suits the work. The image itself starts on less, which is what the second figure is.

--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

Firefox asks for 2 cores and 4 GB. Cheapest first.

E2 Medium

$0.0419/ hour2 cores · 4 GBStart this machine

T3 Medium

$0.052/ hour2 cores · 4 GBStart this machine

B2s

$0.052/ hour2 cores · 4 GBStart this machine

Run Firefox on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start Firefox Browse workflows