workspaces-core-images VS workspaces-issues

The copy script resides within the Core images and can be adjusted if necessary. It is visible in the workspaces-core-images Github Repo

Another option could be to let the servers just boot into webbrowser and then do somethign VDI (Vitual Desktop infrastructure), for example KASAM: https://www.kasmweb.com/ This would also address/ solve/ simplify many of the mentioned issues above.

https://www.kasmweb.com/ is a popular new solution in this space. I've played around with https://docs.linuxserver.io/images/docker-webtop which is based on their kasmvnc and even in the non lossless mode if feels quite snappy.

I read about Kasm Workspaces here on selfhosted and really wanted to try it out on my Ubuntu VPS. Problem is, I use Traefik for my reverse proxy and it's not technically supported by Kasm. There are also very few hits on searches for the two platforms together, and the information that's available is not very helpful. Maybe I'm the only person really interested in this 😂 but after a lot of time spent figuring it out I decided to write my own guide in case someone else is too. This assumes you already have Traefik setup and running on port 443. The files are available at my Github project.

Check out KASM - https://www.kasmweb.com/ - you can actually play many of your Steam games from it with GPU acceleration.

You could spin up something like Kasm Workspaces, Neko or Docker Webtop.

- The Workspaces Images and Workpaces Core images, are both open source projects that include the image dockerfiles and associated scripts for building the end-user containers such as Chrome , Brave, Ubuntu desktop, etc. You can view the code and licenses here: https://github.com/kasmtech/workspaces-images/blob/develop/LICENSE.md , https://github.com/kasmtech/workspaces-core-images/blob/develop/LICENSE.md

Check out https://www.kasmweb.com/. You could setup a persistent profile storage on a linux distro of your choosing and have all the bookmarks saved there or even have it open chrome directly with all your shortcuts right from the website using 2fa to protect everything.

See: https://github.com/kasmtech/workspaces-issues/issues/244

I just made a github bug report over at https://github.com/kasmtech/workspaces-issues/issues/368, but I'm curious to put out feelers and see if anyone else has noticed strange behavior from recent Kasm releases regarding this. Basically, when setting up a new Workspace based on a Windows RDP Server, the username/password field that used to automatically log in the session don't seem to do anything useful anymore. The dark horse possibility is this has something to do with my reverse proxy through Traefik, but my gut says this is unrelated- especially because it behaves the same when logging in and using Kasm locally. Logging in manually still works.

If you'd like to report the details about your upgrade problems , we'd be happy to take a look. You can file it here: https://github.com/kasmtech/workspaces-issues/issues

Hi, this is covered here: https://github.com/kasmtech/workspaces-issues/issues/350

General feedback can be given in this thread. For bugs or detailed troubleshooting it will be easier if you file an issue here: https://github.com/kasmtech/workspaces-issues/issues

Dont forget to leverage the docs, and issue tracker (https://github.com/kasmtech/workspaces-issues)

You may consider mentioning the details of your scenario on a similar open ticket: https://github.com/kasmtech/workspaces-issues/issues/47