configuration to have this work as a kasm workspace

[nate-yorio]

Describe the bug
VNC viewer shows blackscreen when using kasminit for workspace.

To Reproduce
I'm using the following settings:

sytone/obsidian-remote:latest
2 core
GPU count 1/2
inherit CPU allocation method
Registry: https://ghcr.io/

Volume Mappings:
{
"/home/username/nextcloud": {
"bind": "/vaults",
"mode": "rw",
"uid": 1000,
"gid": 1000,
"required": true
}
}

Docker Run Config Override:
{
"user": 1000,
"entrypoint": [
"/kasminit"
],
"environment": {
"PUID": "1000",
"PGID": "1000"
},
"ports": {
"6901/tcp": 6901,
"8080/tcp": 8080,
"8443/tcp": 8443
}
}

My logic for these settings was based on the sort of expectations defined in the docker baseimage from linuxserver.io that is being used in this project.

I couldn't get it to start until I added in kasminit as the entrypoint, but I just get a black screen. So it's like it's not able to load in the startup stuff in autostart or startwm.sh, but I'm not quite sure what I'd have to set to make this custom image compatible.

On their github page for the base image for this they say:
"Kasm Workspaces compatibility

Included in these base images are binary blobs /kasmbins and a special init process /kasminit to maintain compatibility with Kasm Workspaces, If using this base image as reccomended with the startwm.sh or autostart entrypoints. They will be able to be used on that platform without issue."

Thoughts? Advice?

Additionally, I have no idea if the config overrides make sense here, it seems like if you pull the base image into kasm the only config overrides they themselves include are:

{
"user": 1000,
"entrypoint": [
"/kasminit"
]
}

but this doesn't work since this image has custom things on top of the base