← Directory

Chrome

Headless Google Chrome packaged in a lightweight Alpine Linux container, for self-hosted browser automation, scraping, and screenshot capture.

  • Media Applications
  • Media Servers
  • Tools & Utilities
Headless Google Chrome packaged in a lightweight Alpine Linux container, for self-hosted browser automation, scraping, and screenshot capture.

Platform availability

Available on 3 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
40last commit 332 days ago
Popular
672,141 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
208 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 13 days ago

GitHub stars
2,141
Open issues
53
Last commit
2025-11-15
Latest release
89
License
Apache-2.0
Activity
stale

Checked 7 days ago - source: GitHub (jlandure/alpine-chrome)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 1 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 14 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the prompt-api-polyfill package Run npm install prompt-api-polyfill in your project before starting, so the browser AI prompt features are available. If you skip this, the app may error because the polyfill it expects is missing. source
  • Set the backend config file Add your .env.json configuration and assign it to window.FIREBASE_CONFIG, so the app knows which AI backend to use. Without this setting, AI features may fail to connect or behave unexpectedly. source
  • Check if AI features are ready Before creating a summarizer, check availability and user activation so the browser does not block the feature. This prevents first-run failures on machines where the AI API is not supported. source
  • Registry The README warns the image previously published under the Zenika Docker Hub org is no longer linked to this repo; check the README for the current registry. source
  • Usage Runs headless Chrome only; intended for automation, scraping, and screenshots rather than interactive browsing. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where can I pull alpine-chrome if Docker Hub pulls are rate-limited?

The README lists GitHub Container Registry and Google Cloud registries as other registries, but notes they may be deleted or obsolete.

Which alpine-chrome tags should I use when I need Node.js, Puppeteer, Playwright, or Selenium?

There are dedicated tags such as with-node, with-puppeteer, with-playwright, and with-selenoid, along with version-prefixed variants like 100-with-node.

Why might a self-hosted Chrome setup reject a valid-looking server certificate?

Chrome, and possibly Firefox, may stop trusting certificates that have been issued for more than one year. Checking the server certificate duration can explain the failure.

What should I test when Chrome misbehaves behind Nginx Proxy Manager?

Try a new Chrome profile or at least an incognito window. If that fixes it, the issue is likely a Chrome cache problem.

Answers sourced from github.com, www.reddit.com, www.reddit.com

Community

Collected 9 days ago - public community threads