Running Labs
Everything you need to know about running SnapBench labs.
Starting a Lab
From the Dashboard
- Navigate to your Dashboard
- Browse available scenarios
- Click Start Lab on your chosen scenario
- Wait for provisioning (1-2 minutes)
- Click Access Lab when ready
Provisioning
During provisioning, SnapBench:
- Creates an isolated Kubernetes namespace
- Deploys all components
- Sets up networking and access
The status indicator shows progress.
The Lab Interface
┌─────────────────────────────────────────────────────────────┐
│ Header: Scenario name, timer, stop button │
├───────────────────────────────────┬─────────────────────────┤
│ │ │
│ │ Instructions │
│ Component Tabs │ (right sidebar) │
│ (terminals, web UIs) │ │
│ │ │
│ │ │
└───────────────────────────────────┴─────────────────────────┘Component Tabs
The main area shows component interfaces:
| Tab Type | What it shows |
|---|---|
| Terminal | Command-line access to a container |
| Web UI | HTTP interface to a service |
Click tabs to switch between components.
Instructions Sidebar
The right sidebar shows step-by-step instructions:
- Follow steps in order
- Click navigation links to switch components
- Code blocks have copy buttons (hover to reveal)
Using Terminals
Terminals give you shell access to containers.
Running Commands
- Click in the terminal
- Type your command
- Press Enter
Copy/Paste
- Copy: Select text, right-click > Copy (or Ctrl/Cmd+C)
- Paste: Right-click > Paste (or Ctrl/Cmd+V)
Common Issues
| Issue | Solution |
|---|---|
| Terminal not connecting | Wait for pod to be ready, refresh |
| Command not found | Check you're in the right container |
| Permission denied | Some containers run as non-root |
Using Web UIs
Web UIs show service interfaces in an iframe.
Navigation
- Use the UI as normal
- Some UIs may require login (check instructions for credentials)
Opening in New Tab
Click the external link icon to open the UI in a new browser tab.
Lab Timer
Labs have a time limit (TTL):
- The timer shows remaining time
- Labs auto-stop when time expires
- Your instructor sets the TTL
Need More Time?
If you need more time, contact your instructor. They may be able to extend or let you restart.
Stopping a Lab
When finished:
- Click Stop Lab in the header
- Confirm the action
- Your environment is cleaned up
Or simply let the lab expire automatically.
Lab States
| State | Description |
|---|---|
| Starting | Provisioning in progress |
| Running | Lab is active, you can work |
| Stopping | Cleanup in progress |
| Stopped | Lab ended, resources cleaned up |
| Failed | Something went wrong (see troubleshooting) |
Tips for Success
Before Starting
- Read the scenario description
- Check the estimated duration
- Ensure stable internet connection
During the Lab
- Follow instructions carefully
- Use copy buttons for code blocks
- Check component status if something fails
- Don't skip steps—they often build on each other
If Stuck
- Re-read the current instruction
- Check previous steps were completed
- Look for troubleshooting tips in blockquotes
- Ask your instructor for help
Next Steps
- Troubleshooting - Fix common issues
