rancher-troubleshooter

Diagnose Rancher Desktop and Kubernetes health issues on WSL2.

Updated Oct 21, 2025
One-click install
npx skills add https://github.com/Lupus/my-dot-claude --skill rancher-troubleshooter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rancher-troubleshooter
Source: https://github.com/Lupus/my-dot-claude/tree/main/skills/rancher-troubleshooter
Command: npx skills add https://github.com/Lupus/my-dot-claude --skill rancher-troubleshooter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Rancher Desktop running on WSL2 can become slow, misbehave, or fail to start. This skill provides a structured diagnostic workflow to identify root causes and guide remediation for Kubernetes/K3s health issues.

Core Features & Use Cases

  • Systematic diagnostics: guides users through health checks of WSL2, Rancher Desktop, k3s, and etcd to pinpoint root causes.
  • Comprehensive data collection: leverages the bundled script to collect cluster info, node health, component statuses, and recent events.
  • Remediation guidance: references common-issues.md for step-by-step solutions and real-world recovery scenarios.

Quick Start

Run the diagnostic script to generate a report: bash scripts/diagnose-rancher.sh > rancher-diagnostics.txt

Frequently Asked Questions about rancher-troubleshooter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Rancher Desktop on WSL2 when Kubernetes API operations are slow?

To troubleshoot slow Kubernetes API operations in Rancher Desktop on WSL2, run the bundled diagnostic script to collect cluster info, node health, and component statuses, then follow the structured health workflow to pinpoint root causes.

Why does my Rancher Desktop K3s deployment fail to start on WSL2?

Rancher Desktop K3s startup failures on WSL2 can be diagnosed by running the diagnostic script to check WSL2, k3s, and etcd health, then consulting the common issues reference for step-by-step recovery guidance.

Do I need kubectl and WSL2 access to diagnose etcd health issues in Rancher Desktop?

Yes, diagnosing etcd health issues requires kubectl, WSL2, and Rancher Desktop access to execute the bundled diagnostic script and gather the necessary cluster component data for troubleshooting.

What is the best way to collect diagnostic data for pod networking errors in K3s on WSL2?

The best way to collect diagnostic data for pod networking errors is executing the bundled shell script, which gathers cluster info, node health, component statuses, and recent events into a comprehensive report.

How do I fix etcd health problems causing Kubernetes misbehavior in Rancher Desktop?

Fix etcd health problems by running the diagnostic script to collect system data, then referencing the bundled common issues markdown file for step-by-step remediation guidance and real-world recovery scenarios.

What should I do when the Rancher Desktop diagnostic script does not resolve my WSL2 Kubernetes issue?

When the diagnostic script does not resolve your WSL2 Kubernetes issue, consult the bundled references for common issue solutions covering slow operations, etcd health, startup failures, and pod networking errors.