Being able to run ANY Docker container directly in the browser is incredibly useful. The most obvious application is educational environments - this makes it trivial to provide all sorts of software for students to tinker with without needing to run any server-side code anywhere, just some static file hosting.
Being able to do it client-side eliminates the biggest cost barrier (VM time) and risks (people using your VMs for cryptomining) that you encounter trying to offer real 'labs' for users.
> You won't get persistence when you restart the process, but you'll still be able to run code that needs to read and write files.
Since it's Linux and you can give it "network access" (using workarounds such as redirecting via a server), you can just use one of the existing ways to mount a remote filesystem that could be stored on the server (such as NFS, sshfs, ...).
Or bridge/mount to the local browser and store it in indexeddb or whatever.
It already has directory mapping when running outside a browser - maybe there's even an easy way to do this more directly than funneling everything through the virtual network.
