You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can either start by using the 46.1MB (16.65 MB Compressed) [pre-built image](#using-built-image) or [build your own](#build-your-own-image).
11
41
12
42
## Using Built Image
13
-
A [pre-built image](https://hub.docker.com/layers/pezhvak/ocserv) is available with the best configurations out of the box. Follow the instructions below to get up and running.
14
43
15
-
This setup includes:
44
+
A [pre-built image](https://hub.docker.com/r/pezhvak/ocserv) is available with the best configurations out of the box.
45
+
Follow the instructions bellow to get up and running.
46
+
47
+
#### This setup includes:
48
+
16
49
- 2 Device connections for each user (`max-same-clients=2`)
17
50
- Up to 16 clients (`max-clients=16`)
18
51
- 10.10.10.0/24 as the internal IP pool
19
52
- Listens on port 1342 (can be changed by altering port mappings when you run the container)
20
53
- Tunnels DNS to the server (`tunnel-all-dns=true`)
21
54
- No-Route list configured by [CNMan/ocserv-cn-no-route](https://github.com/CNMan/ocserv-cn-no-route)
22
55
23
-
***Note:*** All limits can be increased or set to be unlimited in `ocserv.conf` by [building your own image](#build-your-own-image).
56
+
***Note:*** All limits can be increased or set to be unlimited in `ocserv.conf`
57
+
by [building your own image](#build-your-own-image).
58
+
59
+
### Versioning
60
+
By default `docker-compose.yml` and the instructions written in this document uses the `latest`
61
+
tag of the image which represents the latest commit in the `master` branch. beside that tagged commits
62
+
are also available if you want to make sure no breaking changes enters your setup. checkout
63
+
[tags](https://hub.docker.com/repository/docker/pezhvak/ocserv/tags) in our docker hub repo.
64
+
65
+
However, if you like to get the cutting edge features you can always use the `next` tag
66
+
which represents the latest commit in the `develop` branch.
24
67
25
68
### STEP 1: Generate SSL Certificate
26
-
No matter what, if you want to build the image yourself, run the pre-built one with `docker run` or with `docker-compose`, in all cases you will need
27
-
an SSL certificate, It's up to you how you would like to generate it, perhaps you already have some kind of setup for that on your server,
28
-
in case you don't, use the following [image](https://hub.docker.com/r/certbot/certbot/) to generate one:
29
69
30
-
***Note:*** You need to have a domain pointing to your server IP address and ports 80 and 443 available to be listened by the container for
31
-
letsencrypt ACME challenge verification.
70
+
No matter what, if you want to build the image yourself, run the pre-built one with `docker run` or
71
+
with `docker-compose`, in all cases you will need an SSL certificate, It's up to you how you would like to generate it,
72
+
perhaps you already have some kind of setup for that on your server, in case you don't, use the
73
+
following [image](https://hub.docker.com/r/certbot/certbot/) to generate one:
74
+
75
+
***Note:*** You need to have a domain pointing to your server IP address and ports 80 and 443 available to be listened
76
+
by the container for letsencrypt ACME challenge verification.
Don't worry if you can't create one (most often because ports 80 and 443 are not available on your server or you don't have a domain), a fallback script will generate a self-signed certificate for you inside the container. The only difference is
40
-
a warning message about the certificate not being trusted (due to being self-signed) when logging in.
84
+
can't create one (most often because ports 80 and 443 are not available on your server, or you don't have a domain), a
85
+
fallback script will generate a self-signed certificate for you inside the container. The only difference is a warning
86
+
message about the certificate not being trusted (due to being self-signed) when logging in.
41
87
42
88
### STEP 2: Running Your Container
89
+
43
90
Now that we are done with the certificate, you have to run the container somehow.
44
91
45
-
***NOTE:*** If you haven't generated a certificate in the previous step, remove volume mountings to cert paths in your chosen method. as stated previously
46
-
a self-signed certificate will be generated automatically with the downside of untrusted certificate warning at the logging phase.
92
+
***NOTE:*** If you haven't generated a certificate in the previous step, remove volume mountings to cert paths in your
93
+
chosen method. as stated previously a self-signed certificate will be generated automatically with the downside of
94
+
untrusted certificate warning at the logging phase.
47
95
48
-
### OPTION 1: Docker Compose (Recommended)
96
+
####OPTION 1: Docker Compose (Recommended)
49
97
50
-
I highly recommend using docker-compose for running your container, feel free to change the port by editing `docker-compose.yml`.
98
+
I highly recommend you to use docker-compose for running your container, feel free to change the port by
99
+
editing `docer-compose.yml`. I highly recommend using docker-compose for running your container, feel free to change the
0 commit comments