Browser

A browser that runswhere the machine is

Chromium on a Void Linux desktop of your own.It loads pages from the machine's network, not from yours.

Chromium 151.0.7922.1082 cores · 4 GBOpens in a browser tab

hub://chromium

$ dxflow workflow create --identity chromium hub://chromium --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

The Chrome engine,nothing bolted on

The open-source project behind Chrome, already installed.

The Chrome engine

The same Blink and V8 engine Chrome ships, with none of the extras on top.

It browses from there

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

The profile persists

History, cookies and signed-in sessions stay on the volume between starts.

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 chromium --override env.app.VNC_PASSWORD=something-long

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

The session

The browserfills the screen

Streamed to your browser, with Chromium already maximized.

6082Browserin the tab, at /vnc.html

5901VNCin a native client

/volumeStoragethe profile, cookies and all

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.

Keep the session yoursIt runs without its sandbox here, so do not pass the link around.

Good to know

It runs as root,so keep it to yourself

Inside the container there is one user, and Chromium gives up its sandbox to live with that.

No sandbox

The browser starts with --no-sandbox because root cannot use one. A strong VNC_PASSWORD is what stands in for it.

A browser somewhere else

The traffic leaves from the machine, not from you. That is the point when a site should see a cloud address rather than your own.

The profile belongs on the volume

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

The image

Pulled once,then it stays

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

447Mamd64compressed, the way the registry counts it

443Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/chromium: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

Chromium 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 Chromium on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start Chromium Browse workflows