Skip to content
This repository was archived by the owner on Jun 15, 2021. It is now read-only.

Commit 9fc0596

Browse files
Bot Updating Templated Files
1 parent a1c2f03 commit 9fc0596

File tree

2 files changed

+42
-36
lines changed

2 files changed

+42
-36
lines changed

.github/CONTRIBUTING.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ If you are proposing additional packages to be added, ensure that you added the
9696

9797
### Testing your changes
9898

99-
```
99+
```bash
100100
git clone https://github.com/linuxserver/docker-openvpn-as.git
101101
cd docker-openvpn-as
102102
docker build \
@@ -106,13 +106,14 @@ docker build \
106106
```
107107

108108
The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`
109-
```
109+
110+
```bash
110111
docker run --rm --privileged multiarch/qemu-user-static:register --reset
111112
```
112113

113114
Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64`.
114115

115-
## Update the chagelog
116+
## Update the changelog
116117

117118
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
118119

README.md

+38-33
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!-- DO NOT EDIT THIS FILE MANUALLY -->
2-
<!-- Please read the CONTRIBUTING.md -->
2+
<!-- Please read the https://github.com/linuxserver/docker-openvpn-as/blob/master/.github/CONTRIBUTING.md -->
33

44
[![linuxserver.io](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png)](https://linuxserver.io)
55

@@ -12,13 +12,14 @@
1212

1313
The [LinuxServer.io](https://linuxserver.io) team brings you another container release featuring:
1414

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
2020

2121
Find us at:
22+
2223
* [Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more!
2324
* [Discord](https://discord.gg/YWrKVTn) - realtime support / chat with the community and the team.
2425
* [Discourse](https://discourse.linuxserver.io) - post on our community forum.
@@ -44,7 +45,7 @@ Find us at:
4445

4546
## Supported Architectures
4647

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/).
4849

4950
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.
5051

@@ -63,6 +64,21 @@ This image provides various versions that are available via tags. `latest` tag u
6364
| latest | Stable releases based on ubuntu bionic |
6465
| xenial | DEPRECATED, no longer updated - Stable releases based on ubuntu xenial |
6566

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+
6682
## Usage
6783

6884
Here are some example snippets to help you get started creating a container.
@@ -96,7 +112,7 @@ services:
96112
97113
### docker cli
98114
99-
```
115+
```bash
100116
docker run -d \
101117
--name=openvpn-as \
102118
--cap-add=NET_ADMIN \
@@ -112,7 +128,6 @@ docker run -d \
112128
ghcr.io/linuxserver/openvpn-as
113129
```
114130

115-
116131
## Parameters
117132

118133
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
134149

135150
As an example:
136151

137-
```
152+
```bash
138153
-e FILE__PASSWORD=/run/secrets/mysecretpassword
139154
```
140155

@@ -153,35 +168,17 @@ Ensure any volume directories on the host are owned by the same user you specify
153168

154169
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
155170

156-
```
171+
```bash
157172
$ id username
158173
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
159174
```
160175

161-
162-
&nbsp;
163-
## Application Setup
164-
165-
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-
179176
## Docker Mods
177+
180178
[![Docker Mods](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=openvpn-as&query=%24.mods%5B%27openvpn-as%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml)](https://mods.linuxserver.io/?mod=openvpn-as "view available mods for this container.") [![Docker Universal Mods](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=universal&query=%24.mods%5B%27universal%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml)](https://mods.linuxserver.io/?mod=universal "view available universal mods.")
181179

182180
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.
183181

184-
185182
## Support Info
186183

187184
* 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
198195
Below are the instructions for updating containers:
199196

200197
### Via Docker Compose
198+
201199
* Update all images: `docker-compose pull`
202200
* or update a single image: `docker-compose pull openvpn-as`
203201
* Let compose update all containers as necessary: `docker-compose up -d`
204202
* or update a single container: `docker-compose up -d openvpn-as`
205203
* You can also remove the old dangling images: `docker image prune`
206204

207205
### Via Docker Run
206+
208207
* Update the image: `docker pull ghcr.io/linuxserver/openvpn-as`
209208
* Stop the running container: `docker stop openvpn-as`
210209
* Delete the container: `docker rm openvpn-as`
211210
* 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)
212211
* You can also remove the old dangling images: `docker image prune`
213212

214213
### Via Watchtower auto-updater (only use if you don't remember the original parameters)
214+
215215
* Pull the latest image at its tag and replace it with the same env variables in one run:
216-
```
216+
217+
```bash
217218
docker run --rm \
218219
-v /var/run/docker.sock:/var/run/docker.sock \
219220
containrrr/watchtower \
220221
--run-once openvpn-as
221222
```
223+
222224
* You can also remove the old dangling images: `docker image prune`
223225

224226
**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).
225227

226228
### Image Update Notifications - Diun (Docker Image Update Notifier)
229+
227230
* We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
228231

229232
## Building locally
230233

231234
If you want to make local modifications to these images for development purposes or just to customize the logic:
232-
```
235+
236+
```bash
233237
git clone https://github.com/linuxserver/docker-openvpn-as.git
234238
cd docker-openvpn-as
235239
docker build \
@@ -239,7 +243,8 @@ docker build \
239243
```
240244

241245
The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`
242-
```
246+
247+
```bash
243248
docker run --rm --privileged multiarch/qemu-user-static:register --reset
244249
```
245250

0 commit comments

Comments
 (0)