Hi
Thanks for your code.
I git cloned and checked out only your Alpine Linux branch and installed. But, this is my shell output:
❯ npm run dev
> browser-vm@0.0.0 dev
> vite
VITE v5.4.8 ready in 557 ms
➜ Local: http://localhost:5173/
➜ Network: use --host to expose
➜ press h + enter to show help
Error: spawn /usr/bin/google-chrome ENOENT at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
And, the container image booted up successfully in my browser, but as I am on a Tablet, I couldn't enter "root" at the login prompt. When I select the screen to type, the virtual keyboard is off screen and when the keyboard is back on screen, the field isn't selected, so it is a Catch 22! The hack I have learnt to get the keyboard back in similar situations, which in the Samsung flavour of Android is pressing a particular button, doesn't work in the browser context, like it does in other apps, such as Termux and RVMC Viewer, for example.
Hi
Thanks for your code.
I git cloned and checked out only your Alpine Linux branch and installed. But, this is my shell output:
And, the container image booted up successfully in my browser, but as I am on a Tablet, I couldn't enter "root" at the login prompt. When I select the screen to type, the virtual keyboard is off screen and when the keyboard is back on screen, the field isn't selected, so it is a Catch 22! The hack I have learnt to get the keyboard back in similar situations, which in the Samsung flavour of Android is pressing a particular button, doesn't work in the browser context, like it does in other apps, such as Termux and RVMC Viewer, for example.