Deploy and Host Chrome on Sealos

Chrome is Google's web browser for fast, secure, and customizable web access. This template deploys the LinuxServer.io Chrome container with a Selkies web desktop UI, persistent browser storage, and HTTPS ingress on Sealos Cloud.

About Hosting Chrome

Chrome runs as a single browser desktop service that you access through a web-based interface. The deployment uses the linuxserver/chrome image, starts Chrome automatically, and exposes the Selkies desktop on port 3000 behind a Sealos-managed HTTPS domain.

The template provisions persistent storage for /config, so browser profile data, downloaded files, settings, and extensions can survive container restarts. It also configures HTTP basic authentication, startup/readiness/liveness checks, and a constrained virtual display size to keep resource usage predictable.

This template is intended for personal cloud browsing, testing, demos, and lightweight remote browser workflows. Because browser desktops can expose powerful in-container capabilities, keep the generated password private and avoid sharing the public URL with untrusted users.

Common Use Cases

• Cloud Browser Workspace: Run Chrome from a browser when your local device is locked down or underpowered.
• Web App Testing: Check websites from a clean remote browser profile with persistent settings.
• Remote Troubleshooting: Open pages, reproduce issues, and inspect behavior from a server-side browser session.
• Demo Environments: Provide a controlled browser session for demos, training, or temporary access.
• Persistent Browser Profile: Keep cookies, extensions, bookmarks, and session data across restarts through persistent storage.

Dependencies for Chrome Hosting

The Sealos template includes the required runtime components for hosting Chrome:

• lscr.io/linuxserver/chrome:148.0.7778.178-1-ls95
• A StatefulSet running the Chrome/Selkies container
• Persistent storage mounted at /config
• A Service and HTTPS Ingress for browser access
• A ConfigMap-based launcher that starts Chrome with stable runtime flags

Deployment Dependencies

• Google Chrome - Official Chrome website
• LinuxServer.io Chrome Documentation - Container configuration and runtime options
• linuxserver/docker-chrome GitHub Repository - Upstream image source repository
• Sealos App Store - Chrome template page
• Sealos Discord - Community support

Implementation Details

Architecture Components:

This template deploys the following resources:

• Chrome StatefulSet: Runs the LinuxServer.io Chrome container with a web-accessible Selkies desktop.
• Launcher ConfigMap: Installs an autostart script that launches Chrome with the configured startup URL or CLI flags.
• Persistent Storage: Mounts /config through a 1 GiB PVC for browser profile data and user files.
• Service: Exposes the container's HTTP desktop UI on port 3000 inside the cluster.
• Ingress: Provides a public HTTPS URL through Sealos-managed ingress and certificates.
• App Link: Adds the deployed Chrome URL to the Sealos application view.

Configuration:

The template sets CHROME_CLI from the deployment form, so you can provide a startup URL or Chrome CLI flags. It enables HTTP basic authentication through CUSTOM_USER and a generated password, stores the browser profile under /config, and disables public sharing/collaboration toggles in Selkies by default.

For stable cloud execution, the template uses PIXELFLUX_WAYLAND=false, MAX_RES=4096x2160, SELKIES_ENCODER=jpeg,x264enc, and Chrome launch flags such as --disable-dev-shm-usage. The container uses 200m CPU and 1024Mi memory limits, with requests derived from the Sealos resource ladder.

License Information:

The upstream linuxserver/docker-chrome repository is published under the GPL-3.0 license. Google Chrome itself is distributed under Google's own terms, and users should review the applicable Chrome terms before using the browser in production or shared environments.

Why Deploy Chrome on Sealos?

Sealos is an AI-assisted Cloud Operating System built on Kubernetes that unifies application deployment, operations, storage, networking, and management. By deploying Chrome on Sealos, you get:

• One-Click Deployment: Launch a remote Chrome desktop without writing Kubernetes YAML or operating a server manually.
• Persistent Storage Included: Keep browser data and settings across restarts with built-in persistent volumes.
• Instant Public Access: Receive an HTTPS URL with certificate management handled by Sealos.
• Easy Customization: Update startup URLs, credentials, resources, and storage from Canvas, AI dialog, or resource cards.
• Kubernetes Foundation: Run the browser on a managed Kubernetes platform with standard workload, service, ingress, and storage primitives.
• Resource Efficiency: Use pay-as-you-go resources and adjust CPU, memory, and storage when your workload changes.

Deploy Chrome on Sealos when you need a remote browser quickly and want to spend time browsing or testing instead of maintaining infrastructure.

Deployment Guide

1. Open the Chrome template and click Deploy Now.
2. Configure the parameters in the popup dialog:
   • Chrome startup URL or CLI flags: Set the initial page or extra Chrome flags through CHROME_CLI.
   • Custom user: Set the HTTP basic auth username. The default is abc.
3. Wait for deployment to complete. This typically takes 2-3 minutes. After deployment, you will be redirected to the Canvas. For later changes, describe your requirements in the AI dialog to let AI apply updates, or click the relevant resource cards to modify settings.
4. Access your application via the provided URL:
   • Chrome Web Desktop: Log in with the configured username and generated password, then use Chrome through the web interface.

Configuration

After deployment, you can configure Chrome through:

• AI Dialog: Describe changes such as updating the startup URL, increasing resources, or adjusting environment variables.
• Resource Cards: Open the StatefulSet, Ingress, or storage resource card to modify runtime settings.
• Environment Variables: Tune CHROME_CLI, CUSTOM_USER, PASSWORD, MAX_RES, and Selkies settings.
• Persistent Profile: Browser state is stored under /config; increase storage if you plan to keep large downloads or many extensions.

Scaling

Chrome is deployed as a single-user StatefulSet with one replica. For this template, vertical scaling is usually the right approach:

1. Open the Canvas for your deployment.
2. Click the Chrome StatefulSet resource card.
3. Adjust CPU, memory, or storage according to your workload.
4. Apply the changes in the dialog and wait for the workload to restart.

For heavy pages, video playback, many tabs, or extension-heavy profiles, increase memory before increasing replica count.

Troubleshooting

Common Issues

Chrome opens but pages fail or crash

• Cause: Browser workloads can be memory-sensitive, especially with complex pages or many tabs.
• Solution: Increase the StatefulSet memory limit, close unused tabs, or reduce the virtual display size.

The web desktop is black or Chrome is not visible

• Cause: Desktop stack compatibility or startup timing can prevent the visible browser window from appearing.
• Solution: Confirm the workload is ready, keep PIXELFLUX_WAYLAND=false, and keep the launcher ConfigMap mounted correctly.

Storage fills up

• Cause: Downloads, browser cache, profile data, or crash reports can consume the /config PVC.
• Solution: Remove unnecessary files from the browser profile or increase the PVC size from the storage resource card.

The UI feels slow

• Cause: Remote browser rendering depends on CPU, memory, page complexity, network latency, and display resolution.
• Solution: Increase CPU/memory, close heavy tabs, or lower MAX_RES if you do not need 4K output.

Getting Help

• LinuxServer.io Chrome Documentation
• linuxserver/docker-chrome Issues
• Sealos Discord

Additional Resources

• Chrome Help
• LinuxServer.io Documentation
• Sealos

License

This Sealos template is provided as part of the Sealos templates repository. The upstream linuxserver/docker-chrome project is licensed under GPL-3.0, and Google Chrome is governed by Google's Chrome terms.