hwdsl2/docker-openvpn

docker-openvpn lets you run your own private VPN server on a Linux machine with a single Docker command. Instead of relying on a commercial VPN provider, you set up OpenVPN on a server you control, then connect your laptop, phone, or other devices to it. Your internet traffic routes through your server, which is useful for securing your connection on public Wi-Fi or accessing resources on your home or office network remotely. The main appeal is that it handles the heavy lifting automatically. OpenVPN requires creating a public key infrastructure (PKI), generating certificates, and distributing config files to each device. This project does all of that on first start. You run one command to launch the server, copy the generated config file to your device, and import it into any standard OpenVPN client app to connect. A helper script lets you add new devices, list existing ones, and revoke access for someone who should no longer have it. This is aimed at anyone who wants a self-hosted VPN without manually configuring certificates and security settings. A founder who travels and wants a trusted connection back to a cloud server, or a small team that needs secure remote access, could have it running in minutes. It comes with modern encryption (AES-128-GCM), supports both IPv4 and IPv6, and runs on a lightweight Alpine Linux base. It works across common hardware architectures, including standard 64-bit servers, ARM64 machines like a Raspberry Pi 4, and older ARM devices. Configuration is optional. If you want to change the port, protocol, or DNS servers, you can pass those settings through an environment file. Otherwise, secure defaults are applied automatically. All server and client data persists in a Docker volume, so updating the image to a newer version won't wipe out your keys or existing client profiles. One thing worth noting is that the project sends anonymous, aggregate usage counts to public GitHub release assets after setup. It does not send telemetry or unique user data, and you can disable it entirely by setting a single environment variable.