jolitz-docker
/jolitz-docker
Inventory Docker on a server — containers and compose projects, published ports against the firewall (DOCKER-USER), image age, restart policies, disk use (docker system df). Read-only unless the user asks for a change. Use when the user asks "what runs in Docker on <host>", "docker inventory", "which ports do the containers publish", "docker disk usage", "prune docker on <host>". Do NOT auto-invoke for "is container X up" — that is a quick query.
- Author
- superlab-by-supbrt ↗
- Repository
- jolitz ↗
- Licence
- MIT
- Last repository change
- 03.11.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Inventory Docker on a server — containers and compose projects, published ports against the firewall (DOCKER-USER), image age, restart policies, disk use (docker system df). Read-only unless the user asks for a change. Use when the user asks "what runs in Docker on <host>", "docker inventory", "which ports do the containers publish", "docker disk usage", "prune docker on <host>". Do NOT auto-invoke for "is container X up" — that is a quick query.
Triggers from the description
Arguments
/jolitz-docker [hostname]
Original author description
Inventory Docker on a server — containers and compose projects, published ports against the firewall (DOCKER-USER), image age, restart policies, disk use (docker system df). Read-only unless the user asks for a change. Use when the user asks "what runs in Docker on <host>", "docker inventory", "which ports do the containers publish", "docker disk usage", "prune docker on <host>". Do NOT auto-invoke for "is container X up" — that is a quick query.
How it works
- Workflow
- References
- Scope and limits
SKILL.md preview
---
name: jolitz-docker
argument-hint: "[hostname]"
description: Inventory Docker on a server — containers and
compose projects, published ports against the firewall
(DOCKER-USER), image age, restart policies, disk use
(docker system df). Read-only unless the user asks for a
change. Use when the user asks "what runs in Docker on
<host>", "docker inventory", "which ports do the containers
publish", "docker disk usage", "prune docker on <host>".
Do NOT auto-invoke for "is container X up" — that is a quick
query.
---
# jolitz-docker
What Docker runs on a host, what it exposes and what it
costs in disk. The inventory is read-only. A prune, a pull,
a restart or a port change is a separate step that asks
first, with its `Way back:` line. **Never run
automatically** — only on explicit user request.
## Workflow
1. **Pipeline.** `rules/first-connection.md` in full. Then
the overrides: `memory/custom-rules/jolitz-docker.md` if
present, the host's `memory.md` and `rules.md`. A port the
memory records as "meant to be public" stays quiet in the
report.
2. **Detect.** `command -v docker`; without it, `command -v
podman` (reported, not inventoried: Podman is out of
scope). `docker ps` needs root or the `docker` group:
the privilege ladder from `jolitz-fleet-audit` →
`references/probes.md` (root, `sudo -n`, else
`skipped: needs root`). Unraid hosts: `rules/unraid.md`
first, its Docker layout differs.
3. **Inventory** in one batch from `references/inventory.md`:
engine and firewall backend, containers, compose projects,
restart policies and counts, images, volumes, disk.
4. **Ports against the firewall** from
`references/ports-firewall.md`: every published port,
its bind address, the `DOCKER-USER` rules or the nftables
table that covers it, the host firewall's state.
5. **Report** in the format of `references/report-format.md`.
6. **Memory.** Record the compose projects and the public
ports the user confirmed in `memory.md` (one line per
project; `- Services: docker` where the line exists), so
the next run and `jolitz-housekeeping` stay quiet about
them.
7. **Changes only on request**, each one asked with its way
back (`rules/way-back.md`):
- `docker compose pull` and `up -d` recreate containers:
a restart (`rules/service-reload.md` asks). Way back:
the previous image tag stays local until pruned; pin it
in the compose file.
- `docker system prune` removes stopped containers,
unused networks and dangling images; with `-a` every
unused image; with `--volumes` data. List what it would
remove (`docker system df -v`) before asking; never
`--volumes` without the volume list in the question.
Way back for a pruned volume: none; say so.
- Binding a port to `127.0.0.1` or a `DOCKER-USER` rule:
a firewall change, `AGENTS.md` → Firewall & network.
8. **Record.** `logger -t jolitz "read-only: docker
inventory"` when nothing changed; otherwise the headline
and the local changelog per `rules/changelog.md`.
## References
Read on demand:
- `references/inventory.md` — the read-only batch and how to
read it (states, restart loops, image age, disk).
- `references/ports-firewall.md` — published ports, bind
addresses, `DOCKER-USER`, the nftables backend, severity.
- `references/report-format.md` — the report.
## Scope and limits
- Docker Engine and Compose v2 (`docker compose`). Podman,
Kubernetes and Swarm services are named when seen, not
inventoried.
- `docker inspect` without `--format` prints `Config.Env`,
and that is where passwords live. Always `--format`, never
the whole JSON into the conversation; `.env` files are
secrets (`rules/secrets.md`).
- Whether a newer image exists needs the registry; a pull
downloads and is asked for. The report shows the local
image's age only.
- macOS: Docker Desktop runs in a VM; the Application
Firewall does not filter its ports. Report them as INFO.
FreeBSD has no native Docker.
Files in this package (4)
- SKILL.md 4 KB
- references/inventory.md 3 KB
- references/ports-firewall.md 3 KB
- references/report-format.md 3 KB
Versions
The database has no other skills named jolitz-docker.
Database snapshot: 13.11.2026 · package version 17c1148d7eea (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95docker-helper
Complete Docker operations via CLI - containers, images, networks, volumes, and compose When user mentions Docker, containers, docker commands, Dockerfile, images, docker-compose, or container registry - 96docker
Docker开发专家助手。当用户需要进行Docker镜像构建、容器编排、Dockerfile编写、Docker Compose或容器化部署时调用。 - 100docker-compose
Use when orchestrating multi-container Docker apps from one compose.yaml — services/networks/volumes, build vs image, ports and bind mounts, env_file and ${VAR} interpolation, depends_on with healthcheck conditions, profiles, deploy.resources limits. Docker Compose v5.6.1 CLI… - 100docker-debugger
Debug Docker containers, fix Dockerfile issues, optimize images, and troubleshoot docker-compose. Use when having Docker problems, container issues, or optimizing Docker builds. - 90jolitz-incident
Triage a live problem on one server — "502 on <host>", "load is high", "disk full", "is <host> down?", "the site hangs". Read-only. Builds a timeline from the journal, lists what changed recently (bin/jolitz-log and the host changelog), checks service state, then reports one… - 100ssh-ops
This skill should be used when the user asks to "run a command on a server", "check Docker containers", "restart a service", "read a remote file", "check disk usage", or mentions managing remote infrastructure via SSH. Teaches CLI-first workflow with progressive tool discovery.