Docker Management — Manage Docker containers, images, volumes, and Compose
Docker Management — Manage Docker containers, images, volumes, and Compose
Start with meaning, then move to detail.
This lesson explains Docker Management — Manage Docker containers, images, volumes, and Compose as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When to Use, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Docker Management — Manage Docker containers, images, volumes, and Compose without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Manage Docker containers, images, volumes, and Compose
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03When to Use
Read this after the foundation, then connect it to the previous step.
- 04Prerequisites
Read this after the foundation, then connect it to the previous step.
- 05Quick Reference
Read this after the foundation, then connect it to the previous step.
- 06Procedure
Read this after the foundation, then connect it to the previous step.
- 071. Identify the domain
Read this after the foundation, then connect it to the previous step.
- 082. Container operations
Read this after the foundation, then connect it to the previous step.
- 093. Image management
Read this after the foundation, then connect it to the previous step.
- 104. Docker Compose
Finish here to verify the result and special cases.
Copy only after you understand the effect.
docker --version && docker compose version# Detached service with port mapping
docker run -d --name web -p 8080:80 nginx
# With environment variables
docker run -d -e POSTGRES_PASSWORD=secret -e POSTGRES_DB=mydb --name db postgres:16
# With persistent data (named volume)
docker run -d -v pgdata:/var/lib/postgresql/data --name db postgres:16
# For development (bind mount source code)
docker run -d -v $(pwd)/src:/app/src -p 3000:3000 --name dev my-app
# Interactive debugging (auto-remove on exit)
docker run -it --rm ubuntu:22.04 /bin/bash
# With resource limits and restart policy
docker run -d --memory=512m --cpus=1.5 --restart=unldocker ps # running containers
docker ps -a # all (including stopped)
docker stop NAME # graceful stop
docker start NAME # start stopped container
docker restart NAME # stop + start
docker rm NAME # remove stopped container
docker rm -f NAME # force remove running container
docker container prune # remove ALL stopped containersRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.