Install Linux Web Launcher
Prerequisites
LWL runs in the Webswing Session Pool environment. When an application runs in a separate container, that container provides the application; it does not replace the LWL runtime requirements.
LWL requires 64-bit Linux on amd64 or arm64, with glibc 2.28 or later. Supported distributions include current LTS Ubuntu and Debian releases, Rocky Linux, AlmaLinux, RHEL 8 or later, Fedora 29 or later, and openSUSE Tumbleweed or Leap 15.3 or later.
The application environment must provide the application executable and its dependencies, whether it runs directly on the host or in an application container. The host must provide any graphics or VAAPI drivers required by the application.
LWL supports EGL rendering, although shared-memory (SHM) rendering is preferred. A discrete GPU is not a baseline LWL requirement.
There is no fixed CPU or memory requirement for LWL. Size each Session Pool host for the native application, the LWL compositor and capture runtime, and the expected number of concurrent sessions. Validate the result with a representative workload; the remaining server requirements and sizing guidance are the same as for Webswing for Java.
Install the support package
Download the Linux Web Launcher package for the same Webswing release as the server. Extract webswing-linux-web-launcher-<version>.zip into the Webswing home directory, then restart Webswing.
The package contains both amd64 and arm64 runtimes under webswing-linux-web-launcher/. Webswing selects the runtime that matches the host architecture.
The support package contains the launcher runtime only. It does not install the Linux application that you intend to run.
In a Webswing Cluster, install the package and all applicable dependencies on every Session Pool host that can run the Linux application.
Conditional host dependencies
This section covers only dependencies that LWL itself may require. The application launched through LWL may require additional dependencies, which are outside the scope of this guide.
The following LWL dependencies are conditional:
| Dependency | Required when |
|---|---|
| Xwayland | The application uses the XWAYLAND backend |
Bubblewrap (bwrap) |
App Process Isolation is enabled, or LWL must create a private X11 socket directory because /tmp/.X11-unix is read-only or does not have the sticky bit |
Select WAYLAND for applications that support Wayland. Select XWAYLAND for X11 applications and make sure Xwayland is installed where the Session Pool runs.
The Linux Applications example is available as a separate webswing-example-linux-apps-<version>.zip drop-in. It requires Docker and is intended as an example environment; install it only where the Webswing process and Docker access are trusted. More about the example drop-in can be found in the Quick start section.