How vernette/amneziawg-docker works
This repository packages AmneziaWG as a Docker client/server container. The main workflow is to prepare a peer config, mount it into the container, and start an interface through awg-quick; the config determines the role. The README also documents key and obfuscation-parameter generation and userspace versus kernel operation. Runtime relationships below are based on README statements only; no source excerpts were provided.
Main entry points: compose.yaml Compose setup · entrypoint.sh Interface startup · client.conf Client template · server.conf Server template
Components 11
Container runtime
- Compose setup
compose.yaml - Interface startup
scripts/entrypoint.sh - awg-quick
- Userspace backend
- Kernel backend
Peer configuration
- Client template
examples/client.conf - Server template
examples/server.conf
Key and parameters
- awg key commands
- Obfuscation generator
scripts/awg-genparams.sh
Other components
- Operator
- VPN peer
Connections 11
- Operator → Client template: edits template
README.md - Operator → Server template: edits template
README.md - Operator → Compose setup: starts container
README.md - Compose setup → Interface startup: starts runtime
- Interface startup → awg-quick: starts interfaces
README.md - awg-quick → Userspace backend: uses by default
README.md - awg-quick → Kernel backend: uses if available
README.md - Client template → VPN peer: configures client side
README.md - Server template → VPN peer: configures server side
README.md - Operator → awg key commands: runs key commands
README.md - Operator → Obfuscation generator: runs generator
README.md