iximiuz Labsiximiuz Labs
Main
  • Discover New!
  • Tutorials
  • Challenges
  • Courses
  • Skill Paths
Docker Roadmap
Playgrounds
Vendors
Labs MCP New!
Pricing
  • Blog
  • Docs
  • Our Authors
  • For Creators
  • For Trainers
  • About Us
  • Support
Sign in Sign up
  • Introduction
  • What is iximiuz Labs
  • Our Focus and Approach
  • Getting Started
  • For Linux and DevOps Beginners
  • For Experienced Engineers
  • Showcase Your Skills
  • Learning Materials
  • Challenges
  • Tutorials
  • Courses
  • Skill Paths
  • Roadmaps
  • Playgrounds
  • What are iximiuz Labs Playgrounds
  • How to Use Playgrounds
  • How to SSH into Playgrounds
  • How to Share a Terminal Session
  • How to Expose HTTP/HTTPS Ports
  • How to Forward Local Ports
  • How to Forward Remote Ports
  • How to Expose Local Endpoints
  • Persistent Playgrounds
  • Playground Container Registry
  • Custom Playgrounds
  • Playground Building Blocks
  • Your First Custom Playground
  • Multi-Drive VMs
  • Multi-Machine Playgrounds
  • Multi-Network Playgrounds
  • Init Tasks
  • UI Tabs
  • Custom Rootfs Images
  • Configuring the Playground Registry
  • Sharing and Access Control
  • Playground Manifest Reference
  • Debugging Playgrounds
  • The Debugging Toolbox
  • Debugging Scenarios
  • labctl playground machine Reference
  • Playground Recipes
  • Coding Agent with Browser Access
  • Remote Docker Host
  • Connect to a Playground Kubernetes Cluster
  • Use Kubernetes MCP Server
  • Running VMs Inside Playground VMs (Nested Virtualization)
  • Labs MCP Server
  • What is Labs MCP
  • Connecting Your AI Tool
  • Scopes and Tools
  • Labs MCP in Practice
  • How Labs MCP Works
  • Content Authoring (Pro)
  • How to Publish Content on iximiuz Labs
  • How to Control Access to Your Content
  • Instructor-led Training (Pro)
  • How to Conduct Training on iximiuz Labs
  • How to Restrict Training Materials to Your Students
Documentation Debugging Playgrounds

Debugging Playgrounds

How to troubleshoot a playground run - the debugging toolbox (Play Debug Console, labctl, examinerctl), scenario-by-scenario advice, and the labctl playground machine reference.

The Debugging Toolbox

The tools for inspecting a playground run - the Play Debug Console (play spec, boot conditions, serial console logs, task details), the labctl commands, and examinerctl inside the VM.

Read

Debugging Scenarios

Where to start depending on what is broken - a misbehaving service, failing init tasks, a run that doesn't boot, an unreachable or unresponsive run, or a run that is gone.

Read

labctl playground machine Reference

The per-machine labctl commands in detail - console (serial boot logs), journal (systemd journal streaming), reboot, stop, and restart.

Read