workspaces-images VS workspaces-issues

While I agree using 'VNC' is a little questionable, I do think their use case together with graphical docker containers is rather cool: https://github.com/kasmtech/workspaces-images

I trust you are aware of the general Steam image (https://hub.docker.com/r/kasmweb/steam). Others are interested in sharing feedback and tips you may want to contribute here: https://github.com/kasmtech/workspaces-images/issues/63

- 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

Yes, running Windows applications via WINE is possible, but compatibility is challenging. We have a Dockerfile that installs wine that we've used on various projects. https://github.com/kasmtech/workspaces-images/blob/develop/dockerfile-kasm-wine

Custom Branding: With a paid license you can whitebox the platform using your own logos etc. Without a license, you can still change the background of the main launcher and of course the container images since they are open source, and we encourage you to build and customize your own.

So I'm having a similar issue to OP and created a github issue on your site related to the retroarch container and Vulkan - https://github.com/kasmtech/workspaces-images/issues/58.

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