fix: skip containerd mountinfo marker on WSL2 to avoid false-positive…

[Ulaganathan-K-B]

… container detection

On WSL2 with Docker Desktop, the WSL2 kernel's /proc/self/mountinfo contains containerd entries even when running natively (not inside any container). The is_container() cgroup-v2 fallback scanned mountinfo for 'containerd' as a marker, producing false positives.

Real containers inside WSL are still detected via /.dockerenv, KUBERNETES_SERVICE_HOST, and /proc/1/cgroup checks earlier in the chain. On WSL, only kubepods/crio markers in mountinfo indicate a real container.

Fixes #51935

What does this PR do?

Related Issue

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

How to Test

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform:

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

• This skill is broadly useful to most users (if bundled) — see Contributing Guide
• SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
• No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
• I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs

[alt-glitch]

This was generated by AI during triage.

Duplicate of #51935 — same is_container() WSL2 false-positive (Docker Desktop mounts containerd into the WSL2 kernel) fixed via the same mechanism (is_wsl() early-return that skips the containerd marker while keeping kubepods/crio). #51935 (by @luxles) was opened ~50 min earlier and is the canonical fix; cross-linking here for the maintainer to pick one.

[teknium1]

Thanks for preserving the existing Kubernetes/CRI mountinfo signals while addressing the WSL-specific false-positive path. Current main still returns True for a containerd match in the final mountinfo fallback (hermes_constants.py:945-949), and the PR limits the WSL exception to that marker while adding regression coverage for both the negative containerd case and positive kubepods case.

The discussion-linked #51935 is not an equivalent implementation: its diff returns before inspecting any WSL mountinfo markers, whereas this PR retains kubepods/crio detection.

Automated hermes-sweeper review.