docker-patterns

原文涵盖的主题

• 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

这里只展示节选，请以完整原文和当前要求为准。