olares-doctor

Diagnose Olares app install, crash, image pull, and reachability failures via olares-cli.

5.2k|321|Updated Apr 29, 2024
One-click install
npx skills add https://github.com/beclab/Olares --skill olares-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: olares-doctor
Source: https://github.com/beclab/Olares/tree/main/cli/skills/olares-doctor
Command: npx skills add https://github.com/beclab/Olares --skill olares-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When an Olares app won't install, keeps crashing, can't pull its image, or shows as running but is unreachable, this Skill finds the root cause by correlating evidence from Market, Cluster, and Dashboard instead of guessing.

Core Features & Use Cases

  • Symptom-based routing: Maps stuck installs, CrashLoopBackOff, ImagePullBackOff, unreachable entrances, and resource pressure to dedicated diagnostic procedures.
  • Read-only diagnosis: Gathers pod logs, events, lifecycle states, and resource usage without mutating the system; the only write operation (thirdleveldomain --force-dedupe) requires explicit approval.
  • Image and domain audits: Lists local containerd images with workload reference counts to find unused candidates, and audits duplicate or reserved third-level domains per user zone.
  • Use Case: An app stays in installing forever. The Skill checks whether another app is downloading (normal queue), inspects pod events for scheduling failures, and routes you to the right fix.

Quick Start

Ask the AI to diagnose why my Olares app is stuck in installing and never reaches running.

Frequently Asked Questions about olares-doctor

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

FAQPage Schema
How do I diagnose an Olares app stuck in installing or pending?

Check `olares-cli market status` for the app state, then verify whether another app is downloading since app-service processes one download at a time. If nothing is downloading, inspect pod events and container statuses in the app's namespace for scheduling or pull failures.

How to find the root cause of CrashLoopBackOff on Olares?

Get the pod logs with `olares-cli cluster pod logs <ns>/<pod> -c <container>` and the `--previous` flag for the crashed instance's traceback. Common causes include missing env or secrets, service-link env collisions, and uid 1000 permission issues on userspace mounts.

Why does my Olares app show running but the page is unreachable?

The `running` state only proves entrance TCP reachability, not HTTP health. Check pod readiness, app logs for startup blockers, and the entrance proxy timeout, which defaults to 15 seconds via `options.apiTimeout`.

Can I find and remove unused container images on Olares?

Run `olares-cli doctor images --unused` to list zero-reference images with reclaimable size. The command is read-only and only identifies candidates; cross-check running pods before pruning since tag bumps can make active images look unused.

Does olares-doctor modify my system during diagnosis?

Diagnosis is read-only by default and never restarts, deletes, or scales workloads automatically. The only mutation is `thirdleveldomain --force-dedupe`, which rewrites Application CRs and requires explicit user approval before running.

What should I do when a GPU binding is rejected with node-pressure?

The rejection means the compute binding cannot fit available resources. Free resources or select different devices using `market resume --compute-binding`, and list operable devices with `olares-cli settings compute list`.