docker-patterns
Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.
Target: Cloud, operations & security. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Docker Patterns
- Docker Compose for Local Development
- Standard Web App Stack
- Development vs Production Dockerfile
- Override Files
- Networking
- Service Discovery
- Custom Networks
Docker and Docker Compose best practices for containerized development. Services in the same Compose network resolve by service name: Use containers to test installer behavior against disposable project copies without allowing the test to mutate the source checkout. Run real containers for Linux distributions such as Debian and Ubuntu. macOS cannot run as a Docker container because Docker shares a Linux kernel. Run the same shell-free test entry point natively on macOS. Windows containers require a Windows Docker engine. Run platform-independent logic on a native Windows CI runner and reserve Windows containers for a Windows host. Keep a native Ubuntu/macOS/Windows CI matrix for host-specific paths, command shims, quoting, and filesystem behavior. Do not claim that a Linux container validates macOS or Windows behavior. Pin base images by immutable digest and pin installed CLI versions. Run as a non-root numeric UID/GID when distro account names differ. Mount the repository and source project read-only. Copy the source project into a writable tmpfs workspace before any mutation. Mount /workspace with noexec, UID/GID 1000, and mode=0700 so only the container user can inspect project
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- affaan-m/ECC
- Source file
- pi/core/skills/docker-patterns/SKILL.md
- Fixed revision
- d2ef2680594f9a17526a6e1a2e18b3d242c5d17b
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: affaan-m/ECC · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T15:01:42.976Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.