workspaces-images VS workspaces-stigs

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.

We publish example ansible playbooks , terraform projects , and STIG hardening scripts. While not suitable for all deployment, hopefully it at least shows a bit about the posture of the organization.