import-compose
Skill558 starsChanged 3 years agoApache-2.0View on GitHub
Import Docker Compose files into Kurtosis. Convert docker-compose.yml to Starlark packages or run them directly. Use when migrating existing Docker Compose workflows to Kurtosis.
- Reads credentials
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
- engine-manageSkill
- files-inspectSkill
- gatewaySkill
- graflokiSkill
- 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
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Import Docker Compose files into Kurtosis, either running them directly or converting to Starlark.
- Very specific: line 44
Default is .env in the current directory.
≈ “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
Import Compose
Import Docker Compose files into Kurtosis, either running them directly or converting to Starlark.
Run a Docker Compose file
kurtosis import docker-compose.ymlThis creates an enclave and runs all services defined in the Compose file.
Run with a named enclave
kurtosis import -n my-enclave docker-compose.ymlConvert only (don't run)
Generate Starlark code from a Compose file without executing:
kurtosis import -c docker-compose.ymlThis outputs Starlark that you can save and customize.
Custom .env file
kurtosis import -e ./custom.env docker-compose.ymlDefault is .env in the current directory.
Supported Compose features
Most common Compose features are supported:
- Services with images
- Port mappings
- Environment variables
- Volumes (converted to file artifacts)
- Depends-on (converted to service ordering)
- Networks (Kurtosis handles networking automatically)
Limitations
- Build directives are not supported (images must be pre-built)
- Some advanced networking features may not translate directly
- Volume mounts become file artifacts (not persistent volumes)
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.