mirrors/docker-surfshark
2
0
Fork 0
mirror of https://github.com/ilteoood/docker-surfshark.git synced 2025-12-31 01:47:21 +01:00
Code Issues Projects Releases Wiki Activity

Merge pull request #9 from jmiller148/web-ui

Browse Source 
Allow access to attached container's web ui
This commit is contained in:
Matteo Pietro Dazzi
2020-10-25 21:33:14 +01:00
committed by GitHub
parent 950881c34b 3a324c0ca4
commit 593331d2b7
4 changed files with 18 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
Dockerfile
View File

@@ -9,6 +9,7 @@ ENV SURFSHARK_PASSWORD=
ENV SURFSHARK_COUNTRY=
ENV SURFSHARK_CITY=
ENV CONNECTION_TYPE=tcp
ENV LAN_NETWORK=
HEALTHCHECK --interval=60s --timeout=10s --start-period=30s CMD curl -L 'https://ipinfo.io'
COPY startup.sh .
RUN apk add --update --no-cache openvpn wget unzip coreutils curl && chmod +x ./startup.sh

6
README.md
View File

@@ -19,7 +19,7 @@ The link is established using the [OpenVPN](https://openvpn.net/) client.
## Configuration
The container is configurable using 4 environment variables:
The container is configurable using 5 environment variables:
| Name | Mandatory | Description |
|------|-----------|-------------|
@@ -28,6 +28,7 @@ The container is configurable using 4 environment variables:
|SURFSHARK_COUNTRY|No|The country, supported by SurfShark, in which you want to connect|
|SURFSHARK_CITY|No|The city of the country in which you want to connect|
|CONNECTION_TYPE|No|The connection type that you want to use: tcp, udp|
|LAN_NETWORK|No|Lan network used to access the web ui of attached containers. Comment out or leave blank: example 192.168.0.0/24|
`SURFSHARK_USER` and `SURFSHARK_PASSWORD` are provided at the bottom of this page: [https://account.surfshark.com/setup/manual](https://account.surfshark.com/setup/manual).
@@ -53,6 +54,7 @@ services:
- SURFSHARK_COUNTRY=it
- SURFSHARK_CITY=mil
- CONNECTION_TYPE=udp
- LAN_NETWORK=
cap_add:
- NET_ADMIN
devices:
@@ -95,4 +97,6 @@ If you want to attach a container to the VPN, you can simply run:
sudo docker run -it --net=container:CONTAINER_NAME alpine /bin/sh
```
If you want access to an attached container's web ui you will also need to expose those ports. The attached container must not be started until this container is up and fully running.
If you face network connection problems, I suggest you to set a specific DNS server for each container.

5
docker-compose.yml
View File

@@ -10,12 +10,13 @@ services:
- SURFSHARK_COUNTRY=it
- SURFSHARK_CITY=mil
- CONNECTION_TYPE=udp
- LAN_NETWORK=192.168.0.0/24 #Optional - Used to access attached containers web ui
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun
ports:
- 9091:9091 #we open here the port for transmission, as this container will be the access point for the others
- 9091:9091 #We open here the port for transmission, as this container will be the access point for the others
restart: unless-stopped
dns:
- 1.1.1.1
@@ -37,4 +38,4 @@ services:
#ports:
#- 9091:9091 needed to access transmission's GUI
network_mode: service:surfshark
restart: unless-stopped
restart: unless-stopped

10
startup.sh
View File

@@ -4,6 +4,14 @@ wget -O ovpn_configs.zip https://api.surfshark.com/v1/server/configurations
unzip ovpn_configs.zip -d ovpn_configs
cd ovpn_configs
VPN_FILE=$(ls | grep "${SURFSHARK_COUNTRY}" | grep "${SURFSHARK_CITY}" | grep "${CONNECTION_TYPE}" | shuf | head -n 1)
echo Choosed: ${VPN_FILE}
echo Chose: ${VPN_FILE}
printf "${SURFSHARK_USER}\n${SURFSHARK_PASSWORD}" > vpn-auth.txt
if [ -n ${LAN_NETWORK} ]
then
DEFAULT_GATEWAY=$(ip -4 route list 0/0 | cut -d ' ' -f 3)
ip route add "${LAN_NETWORK}" via "${DEFAULT_GATEWAY}" dev eth0
echo Adding ip route add "${LAN_NETWORK}" via "${DEFAULT_GATEWAY}" dev eth0 for attached container web ui access
echo Do not forget to expose the ports for attached container we ui access
fi
openvpn --config $VPN_FILE --auth-user-pass vpn-auth.txt