Docker DebugSAFE
A platform for packaging and launching blockchain infra. Think docker compose for blockchain
Overview
A platform for packaging and launching blockchain infra. Think docker compose for blockchain
938b496bbe73OBSERVED · 2026-10-14What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: docker-debug
description: Debug 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.
compatibility: Requires Docker and kurtosis CLI.
metadata:
author: ethpandaops
version: "1.0"
---
# Docker Debug
Diagnose and fix issues with Kurtosis running on a local Docker engine.
## Quick triage
```bash
# Check engine is running
kurtosis engine status
# List all kurtosis containers
docker ps -a --filter "label=app.kubernetes.io/managed-by=kurtosis" --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"
# If no label filter works, grep for kurtosis
docker ps -a | grep kurtosis
```
## Engine issues
### Engine won't start
```bash
# Check if old engine is still running
docker ps -a | grep kurtosis-engine
# Check engine logs
docker logs $(docker ps -aq --filter "name=kurtosis-engine") 2>&1 | tail -50
# Nuclear option: stop and remove all kurtosis containers
kurtosis engine stop
docker ps -a | grep kurtosis | awk '{print $1}' | xargs -r docker rm -f
kurtosis engine start
```
### Engine version mismatch
```bash
# Check CLI version
kurtosis version
# Check running engine version
kurtosis engine status
# Force restart with matching version
kurtosis engine restart
```
## Enclave / API container issues
The API container (core/APIC) runs inside each enclave and manages services.
```bash
# List enclaves
kurtosis enclave ls
# Find the APIC container for an enclave
docker ps -a | grep "kurtosis-api"
# View APIC logs (most useful for debugging enclave creation failures)
docker logs $(docker ps -aq --filter "name=kurtosis-api") 2>&1 | tail -100
```
## Service debugging
```bash
# List services in an enclave
kurtosis enclave inspect <enclave-name>
# View service logs
kurtosis service logs <enclave-name> <service-name>
# Follow logs in real time
kurtosis service logs <enclave-name> <service-name> -f
# Shell into a running service
kurtosis service shell <enclave-name> <service-name>
# Execute a command in a service
kurtosis service exec <enclave-name> <service-name> -- <command>
```
## Port and networking issues
```bash
# Check mapped ports for a service
kurtosis enclave inspect <enclave-name>
# Verify port is actually listening inside the container
kurtosis service exec <enclave-name> <service-name> -- netstat -tlnp
# Test connectivity between services (from inside a service)
kurtosis service exec <enclave-name> <service-name> -- wget -qO- http://<other-service>:<port>/endpoint
```
## File artifacts
```bash
# List file artifacts in an enclave
kurtosis enclave inspect <enclave-name>
# Download a file artifact for inspection
kurtosis files download <enclave-name> <artifact-name> /tmp/artifact-output
```
## Common problems
| Symptom | Likely cause | Fix |
|---------|-------------|-----|
| `engine not running` | Engine crashed or was stopped | `kurtosis engine start` |
| Port conflict on start | Old container holding the port | `docker ps -a \| grep kurtosis \| awk '{print $1}' \| xargs docker rm -f` |
| Service unreachable | Wrong port or service not ready | Check `kurtosis enclave inspect` for mapped ports |
| `image not found` | Image not pulled or tag wrong | Check image name in Starlark, try `docker pull <image>` |
| Enclave creation hangs | APIC crash or image pull issue | Check APIC logs: `docker logs` on the kurtosis-api container |
## Cleanup
```bash
# Remove a specific enclave
kurtosis enclave rm <enclave-name>
# Remove all enclaves and clean up
kurtosis clean -a
# Full nuclear clean (if kurtosis clean fails)
docker ps -a | grep kurtosis | awk '{print $1}' | xargs -r docker rm -f
docker network ls | grep kurtosis | awk '{print $1}' | xargs -r docker network rm
kurtosis engine start
```Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
938b496bbe73full audit observations/trust-audit/skill/kurtosis-tech__docker-debug.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-14 | 938b496bbe73 | SAFE | B | 89 | first audit |
Questions
What does the Docker Debug skill do?
A platform for packaging and launching blockchain infra. Think docker compose for blockchain
Is Docker Debug safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Docker Debug access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (938b496bbe73), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.