enclave-inspect
$
npx mdskill add kurtosis-tech/kurtosis/enclave-inspectInspect enclave internals and export state for debugging.
- Reveal running services, ports, and file artifacts inside enclaves.
- Requires kurtosis CLI with a running engine to function.
- Executes commands, dumps logs, and shells into container services.
- Outputs structured text showing enclave status and service details.
SKILL.md
.github/skills/enclave-inspectView on GitHub ↗
--- name: enclave-inspect description: Inspect 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. compatibility: Requires kurtosis CLI with a running engine. metadata: author: ethpandaops version: "1.0" --- # Enclave Inspect Inspect and manage Kurtosis enclaves and their contents. ## List enclaves ```bash kurtosis enclave ls ``` Output shows enclave name, UUID, status (RUNNING/STOPPED), and creation time. ## Inspect an enclave ```bash kurtosis enclave inspect <enclave-name> ``` This shows: - **File Artifacts** — uploaded files and rendered templates - **User Services** — running containers with their ports and status ## Services ### View service details ```bash # Full enclave inspection (shows all services with ports) kurtosis enclave inspect <enclave-name> # View logs for a service kurtosis service logs <enclave-name> <service-name> # Follow logs in real time kurtosis service logs <enclave-name> <service-name> -f # Shell into a service kurtosis service shell <enclave-name> <service-name> # Run a command in a service kurtosis service exec <enclave-name> <service-name> -- <command> ``` ### Access service ports The `inspect` output shows port mappings like: ``` http: 8545/tcp -> http://127.0.0.1:61817 ``` This means port 8545 inside the container is mapped to localhost:61817. On Kubernetes with gateway running, these are forwarded through the gateway. ## File artifacts File artifacts are named blobs of files stored in the enclave. ```bash # List artifacts (shown in enclave inspect) kurtosis enclave inspect <enclave-name> # Download an artifact to local disk kurtosis files download <enclave-name> <artifact-name> /tmp/output-dir # Upload a local file as an artifact kurtosis files upload <enclave-name> /path/to/local/file ``` ## Dump enclave state Export the full enclave state for offline debugging: ```bash kurtosis enclave dump <enclave-name> /tmp/enclave-dump # Verify the dump completed successfully ls -la /tmp/enclave-dump/ ``` This exports: - Service logs - Service configurations - File artifacts - Enclave metadata Useful for sharing with others to debug issues. ## Troubleshooting | Symptom | Cause | Fix | |---------|-------|-----| | Enclave not found | Typo or enclave was removed | Run `kurtosis enclave ls` to see available enclaves | | Dump directory empty | Enclave has no services | Check `kurtosis enclave inspect` — enclave may be idle | | Inspect shows STOPPED services | Services crashed or were stopped | Check logs with `kurtosis service logs` before restarting | | K8s namespace missing | Enclave was cleaned up | Re-run the package to recreate the enclave | ## Enclave lifecycle ```bash # Create an enclave (usually done by kurtosis run) kurtosis enclave add <enclave-name> # Stop an enclave (preserves state) kurtosis enclave stop <enclave-name> # Remove a specific enclave kurtosis enclave rm <enclave-name> # Remove all enclaves kurtosis clean -a ``` ## Kubernetes-specific On Kubernetes, each enclave is a namespace prefixed with `kt-`: ```bash # See enclave namespaces kubectl get ns | grep kt- # See pods in an enclave kubectl get pods -n kt-<enclave-name> # Describe a service pod kubectl describe pod <pod-name> -n kt-<enclave-name> # View pod logs directly kubectl logs <pod-name> -n kt-<enclave-name> ```
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.
- 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.