Docker Patterns
Docker and Compose patterns for local dev stacks, hardened Dockerfiles, networking, volumes, and multi-service orchestration.
- What
- Docker and Compose patterns for local dev stacks, hardened Dockerfiles, networking, volumes, and multi-service orchestration.
- Cost
- Free
- Needs
- Docker (with Compose v2) installed on my machine for the hands-on parts; no account or key is needed to install the skill or to use its default patterns.
- Level
- Intermediate — Docker (with Compose v2) installed on my machine…
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: Docker and Docker Compose best practices for containerized development. The centerpiece is a complete local development stack in Compose: an app service built from the dev stage of a multi-stage Dockerfile with bind mounts for hot reload, a Postgres service with health checks and init scripts, and Redis, wired with depends_on conditions so services start in the right order. Beyond the happy path it covers hardened Dockerfiles, container security basics, networking between services, volume strategies (bind mounts for code, named volumes for data, anonymous volumes to preserve container dependencies), and multi-service orchestration. It also addresses the less glamorous side: building hardened CLI installer harnesses and testing installers across Linux distributions, plus planning accurate native validation on macOS and Windows where containers behave differently. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: the hands-on parts assume Docker is installed and running on your machine; examples lean toward Node.js and Postgres but the Compose patterns transfer to any stack. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Docker Patterns is a free Muse skill that teaches Docker and Docker Compose best practices for containerized development, centered on a complete local development stack with an app service, Postgres with health checks and init scripts, and Redis, wired so services start in the right order. It also covers hardened Dockerfiles, container security, networking, volume strategies, and multi-service orchestration.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Before you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: Docker (with Compose v2) installed on my machine for the hands-on parts; no account or key is needed to install the skill or to use its default patterns. Install "Docker Patterns" for me. It is a Docker and Docker Compose playbook: a standard local dev stack (app, database, cache, local mail testing), multi-stage Dockerfiles with a lean production stage, Compose networking and volume patterns, container hardening and secret handling, debugging commands, and common anti-patterns. It also documents a hardened harness for testing CLI installers inside disposable containers across Linux distributions — read-only mounts, a private temporary workspace, pinned images, no network and no host sign-in information by default — and it says plainly what containers cannot check: macOS and Windows behaviour still needs native runs. Source: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/docker-patterns/SKILL.md (the installer harness it describes lives in the same project, in the docker/plugin-setup folder at its root) Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated October 12, 2026: Skill Harbor regenerated this install prompt from the current upstream file. What changed for you: the command that opens the optional networked session was corrected — it now names the compose file explicitly and adds the --service-ports flag — and a new section explains how to sign the Codex tool in inside that session. In plain terms: by default, the harness keeps your sign-in information out of the container entirely and gives it no network. The networked session is a deliberate opt-in. If you sign Codex in there, its sign-in token stays inside the disposable container (in ~/.codex/auth.json) and is deleted when you remove that container; while the short-lived sign-in bridge runs, other containers on the same Docker network could reach it, so the file advises using a dedicated network and removing the container right after. Passing one of your own keys in from the host is a separate explicit opt-in, and the file itself warns that such a value can be seen and copied for as long as that container lives — remove the container immediately after. The previous prompt described the earlier version, without that section. 1. Download the SKILL.md file into a temporary folder. 2. Compare the file with the fingerprint from Skill Harbor's review of 2026-10-12: - SKILL.md: SHA-256 c0cedeb9b64d4468f5af3bb0a97659c654f0ceb916acbec867a29dc682dd633f If it does not match, the file changed since the review: do not install it yet — tell me what you found and let me decide. 3. Read the file and tell me in plain words: what the skill does when used, whether it connects to a service, whether it reads or sends any personal information or keys, and anything that seems unusual. 4. When I say yes, copy SKILL.md into my skills folder, in a folder named "docker-patterns". 5. Check the copy opens correctly (valid frontmatter, files in place) and tell me what was installed, where, and what is left for me to do (for example: the skill is guidance only and runs nothing by itself; using the installer harness also needs the project's docker/plugin-setup folder from the ECC repository; and the default no-network, no-sign-in-information posture only changes if I deliberately start the networked session). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. If something seems off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.