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
{{ message }}
This repository was archived by the owner on Jun 15, 2021. It is now read-only.
The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`
109
-
```
109
+
110
+
```bash
110
111
docker run --rm --privileged multiarch/qemu-user-static:register --reset
111
112
```
112
113
113
114
Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64`.
114
115
115
-
## Update the chagelog
116
+
## Update the changelog
116
117
117
118
If you are modifying the Dockerfiles or any of the startup scripts in [root](https://github.com/linuxserver/docker-openvpn-as/tree/master/root), add an entry to the changelog
The [LinuxServer.io](https://linuxserver.io) team brings you another container release featuring:
14
14
15
-
* regular and timely application updates
16
-
* easy user mappings (PGID, PUID)
17
-
* custom base image with s6 overlay
18
-
* weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
19
-
* regular security updates
15
+
* regular and timely application updates
16
+
* easy user mappings (PGID, PUID)
17
+
* custom base image with s6 overlay
18
+
* weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
19
+
* regular security updates
20
20
21
21
Find us at:
22
+
22
23
*[Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more!
23
24
*[Discord](https://discord.gg/YWrKVTn) - realtime support / chat with the community and the team.
24
25
*[Discourse](https://discourse.linuxserver.io) - post on our community forum.
@@ -44,7 +45,7 @@ Find us at:
44
45
45
46
## Supported Architectures
46
47
47
-
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
48
+
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
48
49
49
50
Simply pulling `ghcr.io/linuxserver/openvpn-as` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
50
51
@@ -63,6 +64,21 @@ This image provides various versions that are available via tags. `latest` tag u
63
64
| latest | Stable releases based on ubuntu bionic |
64
65
| xenial | DEPRECATED, no longer updated - Stable releases based on ubuntu xenial |
65
66
67
+
## Application Setup
68
+
69
+
The admin interface is available at `https://DOCKER-HOST-IP:943/admin` (assuming bridge mode) with a default user/password of admin/password
70
+
71
+
During first login, make sure that the "Authentication" in the webui is set to "Local" instead of "PAM". Then set up the user accounts with their passwords (user accounts created under PAM do not survive container update or recreation).
72
+
73
+
The "admin" account is a system (PAM) account and after container update or recreation, its password reverts back to the default. It is highly recommended to block this user's access for security reasons:
74
+
1) Create another user and set as an admin,
75
+
2) Log in as the new user,
76
+
3) Delete the "admin" user in the gui,
77
+
4) Modify the `as.conf` file under config/etc and replace the line `boot_pam_users.0=admin` with ~~`#boot_pam_users.0=admin`~~`boot_pam_users.0=kjhvkhv` (this only has to be done once and will survive container recreation)
78
+
* IMPORTANT NOTE: Commenting out the first pam user in as.conf creates issues in 2.7.5. To make it work while still blocking pam user access, uncomment that line and change admin to a random nonexistent user as described above.
79
+
80
+
To ensure your devices can connect to your VPN properly, goto Configuration -> Network Settings -> and change the "Hostname or IP Address" section to either your domain name or public ip address.
81
+
66
82
## Usage
67
83
68
84
Here are some example snippets to help you get started creating a container.
@@ -96,7 +112,7 @@ services:
96
112
97
113
### docker cli
98
114
99
-
```
115
+
```bash
100
116
docker run -d \
101
117
--name=openvpn-as \
102
118
--cap-add=NET_ADMIN \
@@ -112,7 +128,6 @@ docker run -d \
112
128
ghcr.io/linuxserver/openvpn-as
113
129
```
114
130
115
-
116
131
## Parameters
117
132
118
133
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
@@ -134,7 +149,7 @@ You can set any environment variable from a file by using a special prepend `FIL
134
149
135
150
As an example:
136
151
137
-
```
152
+
```bash
138
153
-e FILE__PASSWORD=/run/secrets/mysecretpassword
139
154
```
140
155
@@ -153,35 +168,17 @@ Ensure any volume directories on the host are owned by the same user you specify
153
168
154
169
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
The admin interface is available at `https://DOCKER-HOST-IP:943/admin` (assuming bridge mode) with a default user/password of admin/password
166
-
167
-
During first login, make sure that the "Authentication" in the webui is set to "Local" instead of "PAM". Then set up the user accounts with their passwords (user accounts created under PAM do not survive container update or recreation).
168
-
169
-
The "admin" account is a system (PAM) account and after container update or recreation, its password reverts back to the default. It is highly recommended to block this user's access for security reasons:
170
-
1) Create another user and set as an admin,
171
-
2) Log in as the new user,
172
-
3) Delete the "admin" user in the gui,
173
-
4) Modify the `as.conf` file under config/etc and replace the line `boot_pam_users.0=admin` with ~~`#boot_pam_users.0=admin`~~`boot_pam_users.0=kjhvkhv` (this only has to be done once and will survive container recreation)
174
-
* IMPORTANT NOTE: Commenting out the first pam user in as.conf creates issues in 2.7.5. To make it work while still blocking pam user access, uncomment that line and change admin to a random nonexistent user as described above.
175
-
176
-
To ensure your devices can connect to your VPN properly, goto Configuration -> Network Settings -> and change the "Hostname or IP Address" section to either your domain name or public ip address.
177
-
178
-
179
176
## Docker Mods
177
+
180
178
[](https://mods.linuxserver.io/?mod=openvpn-as"view available mods for this container.")[](https://mods.linuxserver.io/?mod=universal"view available universal mods.")
181
179
182
180
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
183
181
184
-
185
182
## Support Info
186
183
187
184
* Shell access whilst the container is running: `docker exec -it openvpn-as /bin/bash`
@@ -198,38 +195,45 @@ Most of our images are static, versioned, and require an image update and contai
198
195
Below are the instructions for updating containers:
199
196
200
197
### Via Docker Compose
198
+
201
199
* Update all images: `docker-compose pull`
202
200
* or update a single image: `docker-compose pull openvpn-as`
203
201
* Let compose update all containers as necessary: `docker-compose up -d`
204
202
* or update a single container: `docker-compose up -d openvpn-as`
205
203
* You can also remove the old dangling images: `docker image prune`
206
204
207
205
### Via Docker Run
206
+
208
207
* Update the image: `docker pull ghcr.io/linuxserver/openvpn-as`
209
208
* Stop the running container: `docker stop openvpn-as`
210
209
* Delete the container: `docker rm openvpn-as`
211
210
* Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)
212
211
* You can also remove the old dangling images: `docker image prune`
213
212
214
213
### Via Watchtower auto-updater (only use if you don't remember the original parameters)
214
+
215
215
* Pull the latest image at its tag and replace it with the same env variables in one run:
216
-
```
216
+
217
+
```bash
217
218
docker run --rm \
218
219
-v /var/run/docker.sock:/var/run/docker.sock \
219
220
containrrr/watchtower \
220
221
--run-once openvpn-as
221
222
```
223
+
222
224
* You can also remove the old dangling images: `docker image prune`
223
225
224
226
**Note:** We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using [Docker Compose](https://docs.linuxserver.io/general/docker-compose).
* We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
228
231
229
232
## Building locally
230
233
231
234
If you want to make local modifications to these images for development purposes or just to customize the logic:
0 commit comments