# Ops Docker Networking Volumes

> Managing persistent data and complex service-to-service communication.

- Skill: `jcorpac/ops-docker-networking-volumes` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jcorpac/ops-docker-networking-volumes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jcorpac/ops-docker-networking-volumes/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: jcorpac (https://skillmd.com/u/jcorpac)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jcorpac/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.