Graphics

A painting studio,in a browser tab

Krita, on a Void Linux desktop of your own.Brushes, layers and animation, on a machine bigger than your laptop.

Krita 6.0.34 cores · 8 GBOpens in a browser tab
hub://krita

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

Built for painting,not for photos

Krita is an illustration tool first, and the brush engine shows it.

The brush engine

Dozens of engines, stabilizers and wrap-around mode, all of them editable.

Layers that do work

Filter, clone and transform masks that stay live while you keep painting.

Frame-by-frame animation

An onion-skinned timeline, exported to a sequence or a video on the volume.

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 canvas has the whole screen. Show either one to get the desktop back.
AUDIOOff here. Turn it on and an animation plays back with its sound.
start it your way

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

$ dxflow workflow start krita --override env.app.TASKBAR=show --link

The session

The canvasfills the screen

Streamed to your browser, with Krita already maximized.

6082Browserin the tab, at /vnc.html
5901VNCin a native client
/volumeStorageyour files, kept between runs
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 mouse is nota pressure-sensitive pen

The session is streamed as pixels and input, and a tablet on your desk does not reach through it.

No tilt, no pressure

What arrives is cursor position and clicks. Brushes that key off pressure behave as though you pressed the same amount every time.

Canvases cost memory

A large multi-layer painting is a memory problem before it is anything else. Pick the machine for RAM.

Work belongs on the volume

Keep the KRA and the exports under /volume, and the next start opens with your document still there.

The image

Pulled once,then it stays

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

555Mamd64compressed, the way the registry counts it
543Marm64compressed, the way the registry counts it
20GOn diskunpacked, with room to work beside it
ghcr.io/dxflow-ai/krita: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 4 cores and 8 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.

4 cores · 8 GBAsks forwhat the definition writes down
2 cores · 4 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

Krita asks for 4 cores and 8 GB. Cheapest first.

E2 Standard-4
$0.168/ hour4 cores · 16 GBStart this machine
T4g XLarge
$0.168/ hour4 cores · 16 GBStart this machine
C7g XLarge
$0.181/ hour4 cores · 8 GBStart this machine
Run Krita on your own machinePick a machine that meets it, and it opens about a minute after you ask.