context-manage
$
npx mdskill add kurtosis-tech/kurtosis/context-manageSwitch between Kurtosis environments instantly with context commands.
- Manages connections to local, remote, and shared Kurtosis instances.
- Requires kurtosis CLI for all context operations.
- Executes commands based on active context configuration.
- Displays available contexts and current active selection.
SKILL.md
.github/skills/context-manageView on GitHub ↗
--- name: context-manage description: Manage Kurtosis contexts for connecting to different Kurtosis instances. Add, list, switch, and remove contexts. Use when working with multiple Kurtosis environments (local, remote, team shared). compatibility: Requires kurtosis CLI. metadata: author: ethpandaops version: "1.0" --- # Context Manage Manage Kurtosis contexts for connecting to different Kurtosis instances. ## What are contexts? Contexts define which Kurtosis instance the CLI talks to. The default context is `default` which connects to the local engine (Docker or Kubernetes). ## List contexts ```bash kurtosis context ls ``` Shows all configured contexts and which one is active. ## Add a context ```bash kurtosis context add <context-name> ``` ## Switch context ```bash kurtosis context set <context-name> ``` After switching, restart the engine or portal as needed. ## Remove a context ```bash kurtosis context rm <context-name> ``` ## Common workflow ```bash # Check which context is active kurtosis context ls # Switch to a different environment kurtosis context set staging # Verify the switch succeeded kurtosis context ls # Start portal if using a remote context kurtosis portal start # Switch back to local kurtosis context set default ``` ## Error handling | Scenario | Behavior | Resolution | |----------|----------|------------| | Switch to non-existent context | Command fails with error | Run `kurtosis context ls` to see available contexts | | Remove active context | Command fails — cannot remove active | Switch to another context first with `kurtosis context set` | | Engine running after switch | Engine still connected to old context | Run `kurtosis engine restart` after switching contexts |
More from kurtosis-tech/kurtosis
- cli-local-buildBuild and test the Kurtosis CLI from source. Compile the CLI binary locally, run it against Docker or Kubernetes engines, and iterate on CLI changes without creating a release. Use when developing or debugging CLI commands.
- cluster-manageManage Kurtosis cluster settings. Switch between Docker and Kubernetes backends, list available clusters, and configure which cluster Kurtosis uses. Use when you need to change where Kurtosis runs enclaves.
- docker-debugDebug Kurtosis running on local Docker. Inspect engine, API container, and service logs. Diagnose container crashes, port conflicts, and networking issues. Use when kurtosis commands fail or services aren't reachable on Docker.
- docker-local-buildBuild and test Kurtosis from source on local Docker. Compiles all components (engine, core, files-artifacts-expander), builds Docker images, installs the CLI, and restarts the engine. Use when developing Kurtosis and testing changes locally with Docker.
- dumpDump Kurtosis state for debugging and sharing. Export enclave state including service logs, configurations, and file artifacts to a local directory. Use when you need to capture state for offline analysis or to share with others for debugging.
- enclave-inspectInspect and manage Kurtosis enclaves. List enclaves, view services and ports, examine file artifacts, dump enclave state for debugging, and clean up. Use when you need to understand what's running inside an enclave or export its state.
- engine-manageManage the Kurtosis engine server. Start, stop, restart the engine, check status, and view engine logs. Covers both Docker and Kubernetes engine backends. Use when the engine won't start, needs restarting, or you need to check engine health.
- files-inspectInspect, download, upload, and debug Kurtosis file artifacts. View artifacts in an enclave, download them locally for inspection, upload local files, and troubleshoot file mounting issues. Use when services can't find expected files or configs are wrong.
- gatewayStart and manage the Kurtosis gateway for Kubernetes. The gateway forwards local ports to the Kurtosis engine and services running in a k8s cluster. Required when using Kurtosis with Kubernetes. Use when kurtosis engine status shows nothing on k8s or services aren't reachable.
- graflokiStart Grafana and Loki for centralized log collection from Kurtosis enclaves. View aggregated service logs in a Grafana dashboard. Use when you need a UI for browsing logs across multiple services or want persistent log storage.