Sim

Thanks. That means I need to move all data off the hosts on to, say, a NAS - then the NAS becomes the single point of failure. Can I operate a swarm without doing that but still duplicate everything from host 1 to host 2, so host 2 could take over relatively seamlessly (apart from local DNS and moving port forwarding to nginx on the remaining host)?

Thanks. Can I use my existing, single Docker to start a new swarm, or do I have to start from scratch?

Thanks. Could I achieve a simple 2-host solution with Kubernetes though?

So you have Docker itself on a single host (with parts) and all the containers in fault tolerant storage, and the most work you'd have to do in the event of host drive failure is to re-install the OS and Docker itself?

Cool project, thanks!

kasm looks good, thanks - it's definitely in the area; desktop as a service. I want something I can suspect and go back to, not sure if I can do that on kasm or not but a good tip, I'll check it out.

This is not to manage or work on the server, I use terminal and web-based UIs for all of that.

This to host a desktop I can use remotely. Sometimes using my local desktop isn't what I want to do; I might be running a lower power machine, or want to do something I can't on the machine I'm actually using. Or I might want to use a remote Linux desktop from a Windows machine. Sometimes the other way around.

Yes, that's it!

Very useful, reminds me of another browser based Linux manager I forget the name of. Not specifically what I'm trying to achieve but very handy to know, I'll try it. Thanks.

RDP is fine but a brower stream is just as good if the performance works out, I'll give it a look, thanks.

And sugar. Off topic a bit, but my addiction is sugar and some reminders might make the occasional difference.

Openboard with swipe has fixed this for me. Takes a little getting used to but worth it IMO.