Linux Web Launcher quick start
Use this guide to run the Linux Applications example in an existing Webswing deployment. The example provides a browser-based chooser for GIMP and XClock, so you can verify Linux Web Launcher before configuring your own application.
Before you begin
Linux Web Launcher is an optional Webswing runtime; it does not install or start Webswing itself. First complete the Webswing Quick Start to install the server and access the Admin Console. LWL must run on a Linux standalone server or Linux Session Pool host. For server installation on Linux, see Starting on Linux.
Take a quick look at Installation and requirements to confirm that the host meets the Linux Web Launcher requirements, especially the required glibc version.
The Linux Applications example uses Docker and the XWAYLAND backend. Install Docker and Xwayland on the host that runs the Webswing session, and allow the operating-system user that runs Webswing to access the Docker daemon. Use this example only in a trusted environment: access to the Docker daemon is highly privileged.
Start the Linux Applications example
- Verify that the Webswing server and Admin Console are properly installed and can be launched on the Linux host or that the target Linux Session Pool host is available.
- Extract
webswing-linux-web-launcher-<version>.zipinto the home directory of your Webswing distribution. The extracted package containsamd64/andarm64/directories - runtimes for both architectures; Webswing selects the matching runtime automatically. - Obtain
webswing-example-linux-apps-<version>.zipfor the same Webswing release. Do not extract it; copy the ZIP file to<webswing-home>/apps/. - Start or restart Webswing. It automatically deploys the drop-in at
/linux-appsURI. - Open
http://localhost:8080/linux-appsand choose GIMP or XClock.
On its first launch, the example builds the webswing-example-linux-apps:latest Docker image. Allow access to the Ubuntu package repositories and wait for that build to complete - this may take a couple of minutes depending on your environment. Later launches reuse the local image and should be near-instant.
Next steps
The drop-in is an example configuration. To run your own Linux desktop application, see Installation and requirements and Configure a Linux application.