Deploy Arch Linux KDE Plasma Desktop in Your Browser
Arch Linux KDE Plasma desktop in a browser tab with a persistent home.
Just deployed
Deploy and Host Arch Linux KDE Plasma Desktop with Railway
An Arch Linux desktop with KDE Plasma (Wayland) that you open in a browser tab. It comes with Chromium, the Dolphin file manager, the Konsole terminal, Kate and Discover. A generated password protects it, and your home directory (files, settings, browser profile) lives on a persistent volume.
About Hosting Arch Linux KDE Plasma Desktop
A browser desktop needs a display server, a desktop session, a streaming server, a login in front of it, and storage that outlives rebuilds. This community template uses the linuxserver.io image webtop (arch-kde), which streams the desktop with Selkies over a single HTTPS WebSocket. Arch is a rolling release; the image is a snapshot of Arch on its build day (pinned release arch-kde-2025-07-12-ls271), and sudo pacman -Syu inside the desktop brings it up to date until the next redeploy. Railway runs its own init as PID 1, which the image's s6-overlay init refuses to run under, so a small start script brings up the image's own services under s6 supervision instead. nginx requires a login on every page except /healthz. /config (the home directory) is a Railway volume.
Common Use Cases
- A rolling-release KDE workstation to try current Plasma, Qt and toolchain versions without touching your own machine
- Test software and AUR-style builds on Arch from any device with a browser
- Open untrusted links or files in a cloud browser instead of on your own computer
- A ready Linux desktop for workshops, demos and support sessions
Dependencies for Arch Linux KDE Plasma Desktop Hosting
- One service built from a small Dockerfile on top of
lscr.io/linuxserver/webtop(no database, no external API keys) - A Railway volume mounted at
/configfor the home directory
Deployment Dependencies
- linuxserver/docker-webtop (arch-kde branch)
- linuxserver/docker-baseimage-selkies
- Selkies configuration reference
- Selkies web client guide (sidebar, clipboard, files)
- Arch Linux
- Arch Linux Archive
Implementation Details
| Service | What runs inside | Volume | Port |
|---|---|---|---|
| Desktop | KDE Plasma on Wayland (KWin) desktop session, D-Bus, audio, Selkies (loopback only), nginx (login, /healthz), all supervised by s6 | /config | 3000 (public HTTPS domain) |
Plan: Measured on Railway: about 0.57 GB of RAM idle with the KDE session running, also under a 1 GB limit (Trial) after reinstalling packages, so it fits Trial. Free's 0.5 GB is too small. Use Hobby and 2 GB or more for Chromium and larger apps.
First login
- Wait for the deploy to turn healthy (the first build pulls a 2.29 GB compressed image, so allow a few minutes).
- Open the public URL. The browser asks for a login.
- User
arch(or yourCUSTOM_USER; letters, digits and. _ @ -only, otherwise it staysarch), password =PASSWORDfrom the service Variables tab. - The desktop appears and resizes to your browser window. The Selkies side menu has the clipboard box, file upload and download, audio, keyboard and display settings.
Security
- The desktop never runs without a login. Basic auth is on in nginx at build time, and if
PASSWORDis empty, shorter than 8 characters or longer than 256 bytes, the deploy still succeeds but the login is locked with a random password and the deploy log says how to fix it (use 12 or more characters). - Only a hash of the password is stored, and the password is removed from the environment before any desktop app starts.
- Requests from other websites are refused (Origin check in nginx and Selkies), so a page you visit cannot use your cached login to drive the desktop or upload files.
- The Linux user
abchas passwordless sudo. Anyone with the password controls the whole container. The image'sHARDEN_DESKTOP=trueoption disables sudo, terminals and the open-with tools for a locked-down desktop. - Browsers keep basic-auth logins until they close. Use a private window on shared computers.
What persists
Everything in /config: documents, ~/Desktop, desktop settings, browser profiles and apps installed with proot-apps install {app} (proot-apps installs into the home directory). Packages installed with sudo pacman -S live in the image and reset on every redeploy. List them in the PACMAN_PACKAGES variable or in ~/.config/railway-desktop/packages (one or more per line) and they are reinstalled in the background after each start (log: /var/log/railway-desktop/pkg-restore.log). Packages in PACMAN_PACKAGES come from the Arch Linux Archive snapshot that matches the image's build day, so they fit the installed libraries (no partial upgrade). For interactive installs use sudo pacman -Syu {package}.
No GPU: software rendering
Railway has no GPUs. The desktop is drawn on the CPU (Mesa's software renderer), and Selkies encodes the video stream on the CPU. Office work, browsing and development tools run well; 3D apps, games and video editing will be slow. A busy screen costs CPU: lower the frame rate in the side menu, or set SELKIES_FRAMERATE, to save CPU.
Audio and clipboard
- Sound from desktop apps streams to your browser over the same WebSocket. Browsers only play it after you click in the page once.
- Text copy and paste works both ways. Chromium-based browsers ask for clipboard permission. In Firefox and Safari, paste through the clipboard box in the side menu.
Scaling and versions
The desktop is a single-user, volume-backed service: run one replica and scale it vertically. To upgrade, change the FROM line in services/desktop/Dockerfile to a newer arch-kde release tag with its digest and redeploy. The home directory is kept.
Limits
No Docker inside the desktop (Railway runs no privileged containers), no WebRTC/UDP (the WebSocket stream is used instead), and running apps restart on every redeploy. Railway's app sleeping stops the desktop session as well. Use the desktop for your own work: the Fair Use Policy forbids cryptocurrency mining, torrenting, reselling compute, operating proxies or anonymization services, and abusive bots or scrapers.
Why Deploy Arch Linux KDE Plasma Desktop on Railway?
Railway gives the desktop HTTPS, a persistent volume and usage-based billing without any server to manage. You get a Arch desktop at a URL in a few minutes, pay for the RAM and CPU it actually uses, and can resize or redeploy it from the dashboard. This is a community template, not affiliated with linuxserver.io, the Selkies project, the distribution's publishers or Railway.
Template Content
