[{"_1":2,"_155":-5,"_156":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_134":135},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_125":-5,"_126":11,"_127":17,"_128":11,"_129":-5,"_130":11,"_131":-5,"_132":133},"canonicalUrl","https://hub.docker.com/r/darkvex/openvpn-client/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","darkvex","reponame","openvpn-client","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2018-12-27T15:11:28.181955Z","description","Docker openvpn-client","is_private","last_updated","2018-12-27T15:14:17.878131Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",148,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","[![logo](https://raw.githubusercontent.com/dperson/openvpn-client/master/logo.png)](https://openvpn.net/)\n\n# OpenVPN\n\nThis is an OpenVPN client docker container. It makes routing containers'\ntraffic through OpenVPN easy.\n\n# What is OpenVPN?\n\nOpenVPN is an open-source software application that implements virtual private\nnetwork (VPN) techniques for creating secure point-to-point or site-to-site\nconnections in routed or bridged configurations and remote access facilities.\nIt uses a custom security protocol that utilizes SSL/TLS for key exchange. It is\ncapable of traversing network address translators (NATs) and firewalls.\n\n# How to use this image\n\nThis OpenVPN container was designed to be started first to provide a connection\nto other containers (using `--net=container:vpn`, see below *Starting an OpenVPN\nclient instance*).\n\n**NOTE**: More than the basic privileges are needed for OpenVPN. With docker 1.2\nor newer you can use the `--cap-add=NET_ADMIN` and `--device /dev/net/tun`\noptions. Earlier versions, or with fig, and you'll have to run it in privileged\nmode.\n\n**NOTE 2**: If you have connectivity issues, please see the DNS instructions\nbelow.\n\n**NOTE 3**: If you need access to other non HTTP proxy-able ports, please see\nthe Routing instructions below.\n\n**NOTE 4**: If you have a VPN service that allows making local services\navailable, you'll need to reuse the VPN container's network stack with the\n`--net=container:vpn` (replacing 'vpn' with what you named your instance of this\ncontainer) when you launch the service in it's container.\n\n**NOTE 5**: If you need a template for using this container with\n`docker-compose`, see the example\n[file](https://github.com/dperson/openvpn-client/raw/master/docker-compose.yml).\n\n## Starting an OpenVPN client instance\n\n sudo cp /path/to/vpn.crt /some/path/vpn-ca.crt\n sudo docker run -it --cap-add=NET_ADMIN --device /dev/net/tun --name vpn \\\n -v /some/path:/vpn -d dperson/openvpn-client \\\n -v 'vpn.server.name;username;password'\n sudo docker restart vpn\n\nOnce it's up other containers can be started using it's network connection:\n\n sudo docker run -it --net=container:vpn -d some/docker-container\n\n## Local Network access to services connecting to the internet through the VPN.\n\nHowever to access them from your normal network (off the 'local' docker bridge),\nyou'll also need to run a web proxy, like so:\n\n sudo docker run -it --name web -p 80:80 -p 443:443 \\\n --link vpn: -d dperson/nginx \\\n -w \"http://:/;/\"\n\nWhich will start a Nginx web server on local ports 80 and 443, and proxy any\nrequests under `/` to the to `http://:/`. To use\na concrete example:\n\n sudo docker run -it --name bit --net=container:vpn -d dperson/transmission\n sudo docker run -it --name web -p 80:80 -p 443:443 --link vpn:bit \\\n -d dperson/nginx -w \"http://bit:9091/transmission;/transmission\"\n\nFor multiple services (non-existant 'foo' used as an example):\n\n sudo docker run -it --name bit --net=container:vpn -d dperson/transmission\n sudo docker run -it --name foo --net=container:vpn -d dperson/foo\n sudo docker run -it --name web -p 80:80 -p 443:443 --link vpn:bit \\\n --link vpn:foo -d dperson/nginx \\\n -w \"http://bit:9091/transmission;/transmission\" \\\n -w \"http://foo:8000/foo;/foo\"\n\n## Routing for local access to non HTTP proxy-able ports\n\nThe argument to the `-r` (route) command line argument must be your local\nnetwork that you would connect to the server running the docker containers on.\nRunning the following on your docker host should give you the correct network:\n`ip route | awk '!/ (docker0|br-)/ && /src/ {print $1}'`\n\n sudo cp /path/to/vpn.crt /some/path/vpn-ca.crt\n sudo docker run -it --cap-add=NET_ADMIN --device /dev/net/tun --name vpn \\\n -v /some/path:/vpn -d dperson/openvpn-client \\\n -r 192.168.1.0/24 -v 'vpn.server.name;username;password'\n\n**NOTE**: if you don't use the `-v` to configure your VPN, then you'll have to\nmake sure that `redirect-gateway def1` is set, otherwise routing may not work.\n\n**NOTE 2**: if you have a port you want to make available, you have to add the\ndocker `-p` option to the VPN container. The network stack will be reused by\nthe second container (that's what `--net=container:vpn` does).\n\n## Configuration\n\n sudo docker run -it --rm dperson/openvpn-client -h\n\n Usage: openvpn.sh [-opt] [command]\n Options (fields in '[]' are optional, '<>' are required):\n -h This help\n -c '' Configure an authentication password to open the cert\n required arg: ''\n password to access the certificate file\n -d Use the VPN provider's DNS resolvers\n -f '[port]' Firewall rules so that only the VPN and DNS are allowed to\n send internet traffic (IE if VPN is down it's offline)\n optional arg: [port] to use, instead of default\n -m '' Maximum Segment Size \n required arg: ''\n -p '[;protocol]' Forward port \n required arg: ''\n optional arg: [protocol] to use instead of default (tcp)\n -R '' CIDR IPv6 network (IE fe00:d34d:b33f::/64)\n required arg: ''\n add a route to (allows replies once the VPN is up)\n -r '' CIDR network (IE 192.168.1.0/24)\n required arg: ''\n add a route to (allows replies once the VPN is up)\n -v '' Configure OpenVPN\n required arg: ';;'\n to connect to (multiple servers are separated by :)\n to authenticate as\n to authenticate with\n optional arg: [port] to use, instead of default\n\n The 'command' (if provided and valid) will be run instead of openvpn\n\nENVIRONMENT VARIABLES\n\n * `CERT_AUTH` - As above, provide authentication to access certificate\n * `DNS` - As above, Use the VPN provider's DNS resolvers\n * `FIREWALL` - As above, setup firewall to disallow net access w/o the VPN\n * `MSS` - As above, set Maximum Segment Size\n * `ROUTE6` - As above, add a route to allow replies to your internal network\n * `ROUTE` - As above, add a route to allow replies to your private network\n * `TZ` - Set a timezone, IE `EST5EDT`\n * `VPN` - As above, setup a VPN connection\n * `VPNPORT` - As above, setup port forwarding\n * `GROUPID` - Set the GID for the vpn\n\n## Examples\n\nAny of the commands can be run at creation with `docker run` or later with\n`docker exec -it openvpn openvpn.sh` (as of version 1.3 of docker).\n\n### Setting the Timezone\n\n sudo cp /path/to/vpn.crt /some/path/vpn-ca.crt\n sudo docker run -it --cap-add=NET_ADMIN --device /dev/net/tun --name vpn \\\n -v /some/path:/vpn -e TZ=EST5EDT -d dperson/openvpn \\\n -v 'vpn.server.name;username;password'\n\n### VPN configuration\n\nIn order to work you must provide VPN configuration and the certificate. You can\nuse external storage for `/vpn`:\n\n sudo cp /path/to/vpn.crt /some/path/vpn-ca.crt\n sudo docker run -it --cap-add=NET_ADMIN --device /dev/net/tun --name vpn \\\n -v /some/path:/vpn -d dperson/openvpn-client \\\n -v 'vpn.server.name;username;password'\n\nOr you can store it in the container:\n\n cat /path/to/vpn.crt | sudo docker run -it --cap-add=NET_ADMIN \\\n --device /dev/net/tun --name vpn -d dperson/openvpn-client \\\n -v 'vpn.server.name;username;password' tee /vpn/vpn-ca.crt \\\n >/dev/null\n sudo docker restart vpn\n\n### Firewall\n\nIt's just a simple command line argument (`-f \"\"`) to turn on the firewall, and\nblock all outbound traffic if the VPN is down.\n\n sudo cp /path/to/vpn.crt /some/path/vpn-ca.crt\n sudo docker run -it --cap-add=NET_ADMIN --device /dev/net/tun --name vpn \\\n -v /some/path:/vpn -d dperson/openvpn-client -f \"\" \\\n -v 'vpn.server.name;username;password'\n\n### DNS Issues (May Look Like You Can't Connect To Anything)\n\nOften local DNS and/or your ISP won't be accessable from the new IP address you\nget from your VPN. You'll need to add the `--dns` command line option to the\n`docker run` statement. Here's an example of doing so, with a Google DNS server:\n\n sudo cp /path/to/vpn.crt /some/path/vpn-ca.crt\n sudo docker run -it --cap-add=NET_ADMIN --device /dev/net/tun --name vpn \\\n --dns 8.8.4.4 -v /some/path:/vpn -d dperson/openvpn-client \\\n -v 'vpn.server.name;username;password'\n\n# User Feedback\n\n## Issues\n\nIf you have any problems with or questions about this image, please contact me\nthrough a [GitHub issue](https://github.com/dperson/openvpn-client/issues).","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",6447085,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},"content_type","creator",2610685,"full_size",6442582,"id",43203721,"images",[97],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"architecture","amd64","digest","sha256:0d5d971c163b61fee40a9e50b331060826a5cfc66ceb4957fd9fe3585872434c","features","","last_pulled","2026-09-23T15:24:01.134939341Z","last_pushed","2018-12-27T15:14:18Z","os","linux","os_features","os_version","size","variant","2018-12-27T15:14:17.498836Z","last_updater","last_updater_username","media_type","latest","repository",6480924,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":136,"_143":144,"_132":153,"_154":11},{"_36":137,"_38":138,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":139,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":140,"_75":11,"_76":142,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":141},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_145":60,"_146":-5,"_147":-5,"_148":149},"count","next","previous","results",[150],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":151,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},[152],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},[],"canDeleteTags","actionData","errors"]

darkvex/openvpn-client

Tags for darkvex/openvpn-client