hermes - 💡(How to fix) Fix [Feature]: Provide a lightweight Docker image without Playwright/Chromium [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#12572Fetched 2026-04-20 12:18:10
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Timeline (top)
commented ×1
RAW_BUFFERClick to expand / collapse

Problem or Use Case

The official Docker image (nousresearch/hermes-agent) is ~2.4 GB compressed. A significant portion of this size comes from Playwright + Chromium, Node.js, and the WhatsApp bridge — dependencies that many users don't need.

For users who only want CLI chat, gateway mode (Telegram/Discord/Slack), or the API server without browser automation, the current image is unnecessarily large. This makes deployment slower and more expensive, especially on lightweight VPS instances, CI/CD pipelines, or edge environments.

Proposed Solution

Publish an additional Docker image tag (e.g. :slim or :no-browser) that excludes:

  • Playwright and Chromium (~800MB–1GB)
  • Optionally: WhatsApp bridge / Node.js (if not needed for core functionality)

This would bring the image size down to roughly 1.2–1.5 GB or less.

Alternatively, a multi-stage build with a build arg (e.g. INSTALL_BROWSER=true/false) would also work, allowing users to build their own slim variant.

Additional Context

  • The docs already note that browser automation is the most memory-hungry feature and that 1 GB RAM is sufficient without it — a matching slim image would be a natural complement.
  • Currently all tags on Docker Hub (latest, v2026.4.16, v2026.4.13, etc.) are the same full image with no slim/minimal variant available.
  • No existing issue covers this request.

extent analysis

TL;DR

Create a slim Docker image variant by excluding unnecessary dependencies like Playwright, Chromium, and optionally the WhatsApp bridge and Node.js.

Guidance

  • Identify the dependencies that can be safely removed without affecting the required functionality, such as Playwright and Chromium for users who only need CLI chat or gateway mode.
  • Consider using a multi-stage build with a build arg (e.g., INSTALL_BROWSER=true/false) to allow users to build their own slim variant.
  • Evaluate the impact of removing the WhatsApp bridge and Node.js on the core functionality to determine if they can be excluded from the slim image.
  • Test the slim image to ensure it meets the required functionality and performance expectations.

Example

No code snippet is provided as it is not explicitly supported by the issue.

Notes

The proposed solution assumes that the removal of dependencies like Playwright and Chromium will not affect the core functionality for users who do not require browser automation. However, thorough testing is necessary to confirm this assumption.

Recommendation

Apply a workaround by creating a slim Docker image variant, as it allows for a more tailored approach to meet the specific needs of users who do not require browser automation, thereby reducing the image size and deployment costs.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Feature]: Provide a lightweight Docker image without Playwright/Chromium [1 comments, 2 participants]