allanger/container-openvpn
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Activity

commands were deprecated

Browse Source
This commit is contained in:
Alexandre Viau 2014-05-23 18:31:46 -04:00
parent 7be3bf2cd9
commit 93d12716c5
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -3,8 +3,8 @@
Quick instructions: Quick instructions:
```bash ```bash
CID=$(docker run -d -privileged -p 1194:1194/udp -p 443:443/tcp jpetazzo/openvpn) CID=$(docker run -d --privileged -p 1194:1194/udp -p 443:443/tcp jpetazzo/openvpn)
docker run -t -i -p 8080:8080 -volumes-from $CID jpetazzo/openvpn serveconfig docker run -t -i -p 8080:8080 --volumes-from $CID jpetazzo/openvpn serveconfig
``` ```
Now download the file located at the indicated URL. You will get a Now download the file located at the indicated URL. You will get a
@ -48,7 +48,7 @@ on 443/tcp).
The configuration is located in `/etc/openvpn`, and the Dockerfile The configuration is located in `/etc/openvpn`, and the Dockerfile
declares that directory as a volume. It means that you can start another declares that directory as a volume. It means that you can start another
container with the `-volumes-from` flag, and access the configuration. container with the `--volumes-from` flag, and access the configuration.
Conveniently, `jpetazzo/openvpn` comes with a script called `serveconfig`, Conveniently, `jpetazzo/openvpn` comes with a script called `serveconfig`,
which starts a pseudo HTTPS server on `8080/tcp`. The pseudo server which starts a pseudo HTTPS server on `8080/tcp`. The pseudo server
does not even check the HTTP request; it just sends the HTTP status line, does not even check the HTTP request; it just sends the HTTP status line,