Alpine 3.24 KDE Plasma Desktop in Your Browser
Deploys an Alpine Linux 3.24 KDE Plasma desktop that you open in a browser tab, with Chromium, Firefox, Dolphin, Konsole and KDE Discover. A generated password protects it and the home directory sits on a volume.
What you get
- One service built on the linuxserver.io webtop image (release alpine-kde-b1bc61ac-ls152), streamed to the browser with Selkies over one HTTPS WebSocket
- nginx login on every page except /healthz; user alpine (or CUSTOM_USER) and the PASSWORD variable
- A Railway volume at /config holding documents, desktop settings and browser profiles
- Apps installable into the home directory with proot-apps; apk packages can be re-installed after each start via APK_PACKAGES
- Text clipboard both ways, file upload and download, and audio in the browser
Good for
- Working in a full Linux environment from any device with a browser
- Testing apps on Alpine's musl-based system
- Opening untrusted links or files in a cloud browser instead of your own machine
- A ready Linux environment for training, demos and support sessions
Cost
Measured on Railway: 0.55 to 0.8 GB of RAM with one browser session connected and no apps open. RAM is the main cost driver on usage billing; a browser and larger apps need more, and the template notes suggest 2 GB or more on Hobby.
Services in this template
- Desktop · from
baranberkay96/alpine-kde-desktop-railway
Questions people ask
How do I log in?
Open the public URL once the deploy is healthy (the first build pulls a 1.6 GB image). The browser asks for a login: user alpine, or your CUSTOM_USER, and the PASSWORD value from the service Variables tab. If PASSWORD is empty or shorter than 8 characters, the login is locked with a random password and the deploy log says so.
What persists across redeploys?
Everything in /config: documents, desktop settings, browser profiles and proot-apps installs. Packages added with sudo apk add live in the image and reset on redeploy, unless you list them in APK_PACKAGES. Running apps restart on every redeploy.
What are the limits?
Railway has no GPU, so the desktop is rendered on the CPU. Office work, browsing and development tools run well, while 3D apps, games and video editing will be slow. There is no Docker inside the desktop and no WebRTC. Use one replica and scale vertically.
Is it safe to leave running?
Treat the password as full control: the Linux user has passwordless sudo, so anyone with the password controls the whole container. Setting HARDEN_DESKTOP=true disables sudo, terminals and open-with tools. Railway's Fair Use Policy applies, for example no mining, torrenting or proxy services.
What licence notes apply?
The base image and parts of it are GPL-3.0 (webtop and baseimage-selkies), Selkies is MPL-2.0, and the template's own files are GPL-3.0-or-later. Each Alpine package keeps its own licence.
Full template README
Deploy and Host Alpine 3.24 KDE Plasma Desktop with Railway
A KDE Plasma desktop on Alpine Linux 3.24 that you open in a browser tab. It comes with Chromium, Firefox, the Dolphin file manager, the Konsole terminal and KDE Discover. A generated password protects it, and your home directory (files, settings, browser profile) lives on a persistent volume.
About Hosting Alpine 3.24 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 (pinned release alpine-kde-b1bc61ac-ls152), which streams the desktop with Selkies over a single HTTPS WebSocket. 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
- Work in a full Linux environment from any device with a browser, including managed work laptops
- A small, musl-based KDE system for testing apps on Alpine
- Open untrusted links or files in a cloud browser instead of on your own computer
- A ready Linux environment for training sessions, demos and support work
Dependencies for Alpine 3.24 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 (alpine-kde branch)
- linuxserver/docker-baseimage-selkies
- Selkies configuration reference
- Selkies web client guide (sidebar, clipboard, files)
- Alpine Linux releases
Implementation Details
| Service | What runs inside | Volume | Port |
|---|---|---|---|
| Desktop | 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: 0.55 to 0.8 GB of RAM with one browser session connected and no apps open. It runs within Trial's 1 GB (tested with a 1 GB limit); Free's 0.5 GB is too small. Use Hobby and 2 GB or more for a browser and larger apps.
First login
- Wait for the deploy to turn healthy (the first build pulls a 1.6 GB image, so allow a few minutes).
- Open the public URL. The browser asks for a login.
- User
alpine(or yourCUSTOM_USER; letters, digits and. _ @ -only, otherwise it staysalpine), 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 login is locked with a random password and the deploy log says so (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 apk add live in the image and reset on every redeploy. List them in the APK_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).
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 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 Alpine 3.24 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 Linux 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.
Guides for this template
View Alpine 3.24 KDE Plasma Desktop in Your Browser on railway.com
Similar templates
| Template | Category | DeploymentsDeploys |
|---|---|---|
| Chatwoot A customer communication platform | Other | 5,871 |
| Ubuntu-Linux Ubuntu terminal accessible via web browser | Other | 4,926 |
| Ubuntu SSH + Claude ARA TM —SSH server with root access + Claude Code pre-installed. | Other | 4,682 |
| Debian-Linux Debian terminal accessible via web browser. | Other | 2,883 |
| Code Server VS Code in the browser | Other | 2,787 |
| Kali Linux (Web Terminal) Instant Kali Linux browser terminal powered by ttyd | Other | 2,632 |