# Ops Docker Networking Volumes > Managing persistent data and complex service-to-service communication. Use when this capability is needed. - Skill: `tomevault-io/ops-docker-networking-volumes` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/ops-docker-networking-volumes` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/ops-docker-networking-volumes/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: DevOps & Infra - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/ops-docker-networking-volumes --- # Docker Networking & Volumes Containers are ephemeral; your data shouldn't be. ## Volumes & Persistence - **Named Volumes**: Managed by Docker, best for databases and persistent app state. - **Bind Mounts**: Direct host-to-container mapping, best for development code. ## Internal Networking - **User-Defined Bridges**: Created isolated networks for containers to talk to each other via service names (DNS). - **Aliases**: Give containers multiple network identities. ## Best Practices - **External Networks**: Avoid using the default "bridge" network for production. - **Volume Backups**: Regularly back up persistent volumes. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/jcorpac) — claim your Tome and manage your conversions.