engine-manage
Skill558 starsChanged 3 years agoApache-2.0View on GitHub
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.
In this repository21 other files it gives its agents.
- cleanSkill
- cli-local-buildSkill
- cluster-manageSkill
- context-manageSkill
- docker-debugSkill
- docker-local-buildSkill
- dumpSkill
- enclave-inspectSkill
- files-inspectSkill
- gatewaySkill
- graflokiSkill
- import-composeSkill
- k8s-clean-clusterSkill
- k8s-debug-podsSkill
- k8s-dev-deploySkill
- lintSkill
- portalSkill
- port-forwardSkill
- run-packageSkill
- service-manageSkill
- starlark-devSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 74
When running on Kubernetes:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Engine Manage
Manage the Kurtosis engine server lifecycle.
Status
kurtosis engine statusShows whether the engine is running and its version.
Start
# Start with default settings
kurtosis engine start
# Start with debug images
kurtosis --debug-mode engine startOn 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
kurtosis engine stopRestart
kurtosis engine restartEquivalent to stop + start. Useful after changing cluster settings or upgrading.
View logs
kurtosis engine logsDumps engine server logs. Useful for diagnosing startup failures or API errors.
Docker vs Kubernetes
# 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 k8sEngine on Kubernetes
When running on Kubernetes:
# 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 |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.