docker-manager
Skill48 starsChanged 5 months agoMITView on GitHub
Build, run, and manage Docker containers and images. Use when the user mentions Docker, containers, images, docker-compose, or containerized deployment.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-hardeningSkill
- api-builderSkill
- arxiv-watcherSkill
- data-analystSkill
- diagram-makerSkill
- github-workflowSkill
- google-workspaceSkill
- hermeshub-reviewerSkill
- hermes-workspaceSkill
- notion-integrationSkill
- paperclipSkill
- project-plannerSkill
- react-reasoningSkill
- relay-for-telegramSkill
- scraplingSkill
- security-auditorSkill
- Skill FactorySkill
- slack-botSkill
- synapse-swarmSkill
- test-runnerSkill
- web-researcherSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Create a multi-stage Dockerfile for minimal final image
- Very specific: line 40
Create docker-compose.yml with service definitions
- Distinctive: line 52
Use .dockerignore to exclude unnecessary files
- Distinctive: line 54
Use multi-stage builds to reduce final image size
- Distinctive: line 55
Run as non-root user in production
- Distinctive: line 56
Use HEALTHCHECK for container health monitoring
- Distinctive: line 59
Never store secrets in Dockerfiles or images
- Distinctive: line 60
Avoid running as root in production containers
≈ “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
Docker Manager
Container lifecycle management with production-ready patterns.
When to Use
- User mentions Docker, containers, images, or Dockerfiles
- User wants to containerize an application
- User needs docker-compose orchestration
- User asks about container debugging or optimization
Procedure
Building Images
- Analyze the project to determine base image and dependencies
- Create a multi-stage Dockerfile for minimal final image
- Build:
docker build -t name:tag . - Verify:
docker images | grep name
Running Containers
- Run:
docker run -d --name my-app -p 8080:3000 name:tag - Check logs:
docker logs -f my-app - Exec into:
docker exec -it my-app /bin/sh
Docker Compose
- Create docker-compose.yml with service definitions
- Start:
docker compose up -d - Monitor:
docker compose logs -f - Scale:
docker compose up -d --scale web=3
Cleanup
- Stop containers:
docker stop $(docker ps -q) - Remove containers:
docker container prune - Remove images:
docker image prune -a - Remove volumes:
docker volume prune
Best Practices
- Use .dockerignore to exclude unnecessary files
- Pin base image versions (node:20-alpine, not node:latest)
- Use multi-stage builds to reduce final image size
- Run as non-root user in production
- Use HEALTHCHECK for container health monitoring
Pitfalls
- Never store secrets in Dockerfiles or images
- Avoid running as root in production containers
- Watch for large context sizes slowing builds
- Handle signal propagation for graceful shutdown
Verification
- Container running:
docker ps | grep name - Health check passing:
docker inspect --format='{{.State.Health}}' name - Logs clean:
docker logs --tail 50 name
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.

