Bottom Line: Firefox in Kasm Is an On-Demand Browser Workspace, Not a Normal Desktop App Installed Into CasaOS
The 2024 BigBearCasaOS post framed the process as “install Firefox on CasaOS,” but Kasm's architecture is different. Firefox runs as a Kasm Workspace session inside a container and is streamed to the browser through Kasm's web interface.
Size the Kasm Host Before Adding Browser Sessions
Current Kasm requirements start at 2 CPU cores, 4 GB RAM and 50 GB SSD, and each default workspace session has its own CPU and memory allocation. The Kasm system requirements is the current baseline.
The ZimaOS VM requirements is useful if you prefer to isolate Kasm from the NAS app stack.
Use the Current Kasm Workspace Registry
Modern Kasm releases manage browser and desktop workspaces through the registry rather than relying on an old CasaOS catalog definition. Kasm's Kasm workspace updates explains that old workspace images may become incompatible after Kasm upgrades.
A Dedicated Linux VM Is Cleaner for Long-Lived Kasm Deployments
Kasm recommends a single-purpose machine where possible and supports Ubuntu and Debian directly. A VM keeps Kasm's Docker version, swap, session storage and update lifecycle separate from ZimaOS or CasaOS infrastructure.
The ZimaOS app requirements helps decide whether Kasm belongs on the same host.
Do Not Expose the Kasm Login Without HTTPS
Kasm sessions can contain browser cookies, credentials and downloaded files. Keep the management/login interface behind HTTPS and strong authentication, especially if users connect from outside the LAN.
