engine-manage
$
npx mdskill add kurtosis-tech/kurtosis/engine-manageControl the Kurtosis engine lifecycle by starting, stopping, or checking its operational status.
- Diagnose connectivity issues or troubleshoot engine failures requiring a service restart.
- Interacts with the Kurtosis CLI, supporting both Docker and Kubernetes backends.
- Executes specific commands (start, stop, logs, status) based on the required engine action.
- Outputs status reports, logs, or confirmation messages detailing the engine's current state.
SKILL.md
.github/skills/engine-manageView on GitHub ↗
--- name: engine-manage description: Manage 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. compatibility: Requires kurtosis CLI. Docker or Kubernetes cluster access depending on backend. metadata: author: ethpandaops version: "1.0" --- # Engine Manage Manage the Kurtosis engine server lifecycle. ## Status ```bash kurtosis engine status ``` Shows whether the engine is running and its version. ## Start ```bash # Start with default settings kurtosis engine start # Start with debug images kurtosis --debug-mode engine start ``` On Kubernetes, the engine runs as a pod in a `kurtosis-engine-*` namespace. You also need to run `kurtosis gateway` to access it from your local machine. ## Stop ```bash kurtosis engine stop ``` ## Restart ```bash kurtosis engine restart ``` Equivalent to stop + start. Useful after changing cluster settings or upgrading. ## View logs ```bash kurtosis engine logs ``` Dumps engine server logs. Useful for diagnosing startup failures or API errors. ## Docker vs Kubernetes ```bash # Check which backend is active kurtosis cluster get # Switch to Docker kurtosis cluster set docker kurtosis engine restart # Switch to Kubernetes kurtosis cluster set kubernetes kurtosis engine restart kurtosis gateway # Required for k8s ``` ## Engine on Kubernetes When running on Kubernetes: ```bash # The engine runs in its own namespace kubectl get ns | grep kurtosis-engine # Check engine pod kubectl get pods -n <engine-namespace> # View engine logs directly kubectl logs <engine-pod> -n <engine-namespace> # Start the gateway (required for local CLI to reach k8s engine) kurtosis gateway & ``` ## Common issues | Symptom | Fix | |---------|-----| | `No Kurtosis engine is running` | Run `kurtosis engine start` | | Engine starts but `engine status` shows nothing (k8s) | Start the gateway: `kurtosis gateway` | | Version mismatch warning | `kurtosis engine restart` to match CLI version | | Engine start hangs (k8s) | Check pods: `kubectl get pods -A \| grep kurtosis` | | Old engine blocking new start | `kurtosis engine stop` then clean namespaces |
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.
- context-manageManage 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).
- 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.
- 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.