You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What you are looking at is me trying to fix this issue. It seems as though ulimits arent assigned or used properly. Granted, I use Podman, but this should not matter in the end... I think?
I tried troubbleshooting this with ChatGPT and I have experienced similiar issues with TubeArchivist before, which is where those other sysctl settings are from.
Basically: Kasm runs out of threads, fast.
Expected Behavior
I wanted to use Kasm as a makeshift browser based RetroArch and to access tools that I do not have access to at work for one reason or another. So, selfhosting Kasm seemed like my best bet, and it would make for a great platform to start other hosted app projects in the future.
However, when launching an app - that isn't Doom - the entire DinD infra goes completely out of whack. But, it does stay consistent as it does not affect any of my other containers or systems. x) So it just ... implodes. Literally.
Attempt to pop into the container via exec. Run some commands, the error will appear within less than a minute.
Environment
- OS: Armbian 24.11.1 (= Debian 12 Bookworm)
- How docker service was installed:
* See YAML above for deployment
* Using Podman 4.3.1
* Using Docker-Compose 1.29.2
CPU architecture
arm64
Docker creation
Above
Container logs
Kasm puts its logs into separate files. But sure, have some logs :)
root@superdiskboi /s/k/d/k/1.16.1# pwd
/srv/kasm/data/kasm/1.16.1
root@superdiskboi /s/k/d/k/1.16.1# tar cvfz /mnt/stash/kasm-logs.tar.gz -C log/ .
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
Take a look here:
And, here:
What you are looking at is me trying to fix this issue. It seems as though
ulimits
arent assigned or used properly. Granted, I use Podman, but this should not matter in the end... I think?I tried troubbleshooting this with ChatGPT and I have experienced similiar issues with TubeArchivist before, which is where those other sysctl settings are from.
Basically: Kasm runs out of threads, fast.
Expected Behavior
I wanted to use Kasm as a makeshift browser based RetroArch and to access tools that I do not have access to at work for one reason or another. So, selfhosting Kasm seemed like my best bet, and it would make for a great platform to start other hosted app projects in the future.
However, when launching an app - that isn't Doom - the entire DinD infra goes completely out of whack. But, it does stay consistent as it does not affect any of my other containers or systems. x) So it just ... implodes. Literally.
Steps To Reproduce
exec
. Run some commands, the error will appear within less than a minute.Environment
CPU architecture
arm64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: