nordvpn
wireguard-go-docker
Our great sponsors
nordvpn | wireguard-go-docker | |
---|---|---|
50 | 2 | |
695 | 176 | |
- | - | |
3.5 | 4.0 | |
24 days ago | about 2 months ago | |
Shell | Dockerfile | |
GNU Affero General Public License v3.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nordvpn
- [Self Hosted] VPN Mullvad pour les conteneurs Docker
- [Nord Vpn] Après la mise à jour: /run/nordvpn/nordvpnd.sock introuvable
-
Nordlynx, qbittorrent, sonarr, radarr, jellyfin, and jellyseer
version: "3.8" services: nordlynx: image: ghcr.io/bubuntux/nordlynx cap_add: - NET_ADMIN # Required environment: # Review https://github.com/bubuntux/nordvpn#environment-variables - PRIVATE_KEY=mykey # Required - CONNECT=United_States - NET_LOCAL=10.20.30.40/24 # So it can be accessed within the local network - ALLOWED_IPS=10.20.30.40/24 ports: - "6881:6881" #qbittorent - "6881:6881/udp" #qbittorrent - "8080:8080" #qbittorrent - "7878:7878" #radarr - "8989:8989" #sonarr - "9696:9696" #prowlarr - "8097:8096" #jellyfin - "5055:5055" #jellyseer sysctls: - net.ipv6.conf.all.disable_ipv6=1 # Recomended if using ipv4 only qbittorrent: image: linuxserver/qbittorrent container_name: qbittorrent network_mode: service:nordlynx environment: volumes: - /path/to/qbittorrent/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped radarr: image: linuxserver/radarr container_name: radarr network_mode: service:nordlynx environment: volumes: - /path/to/radarr/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped sonarr: image: linuxserver/sonarr container_name: sonarr network_mode: service:nordlynx environment: volumes: - /path/to/sonarr/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped prowlarr: image: linuxserver/prowlarr container_name: prowlarr network_mode: service:nordlynx environment: volumes: - /path/to/prowlarr/config:/config depends_on: - nordlynx restart: unless-stopped jellyfin: image: linuxserver/jellyfin container_name: jellyfin network_mode: service:nordlynx environment: - JELLYFIN_PublishedServerUrl=http://10.20.30.184:8097/ volumes: - /path/to/jellyfin/config:/config - /path/to/jellyfin/cache:/cache - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped jellyseer: image: fallenbagel/jellyseerr:latest container_name: jellyseer network_mode: service:nordlynx environment: volumes: - /path/to/jellyseer/config:/app/config depends_on: - nordlynx restart: unless-stopped
-
KASM with VPN?
All the infos you need are on the github page > https://github.com/bubuntux/nordvpn
-
NordLynx with docker for torrenting | Transmission and QbitTorrent
Issues · bubuntux/nordvpn (github.com)
-
Docker Image - Invalid Username or Password Bug
On https://github.com/bubuntux/nordvpn it mentions that token login is also supported (Nord v3.15.0+). I've used the token login and it works well for me.
- NordVPN bittorrent contaner inside openmediavault
-
Extremely Slow Torrenting Speed
There has been an issue reported on github: https://github.com/bubuntux/nordvpn/issues/367
-
Meshnet on opnsense router
Two of the popular containers are https://github.com/qdm12/gluetun and https://github.com/bubuntux/nordvpn but it's not clear if either of them can use meshnet.
-
VPN gateway on home server VM
A ubuntu/debian vm with nordvpn official client, use iptables to forward this connection to the vm IP. I've seen a similar approach using docker here https://github.com/bubuntux/nordvpn but this only shares connection to other dockers ct's in the same setup
wireguard-go-docker
-
Our User Mode WireGuard Year
I thought wireguard-go requires the kernel tun device. See for example this Docker image for wireguard-go which maps the tun device and requires elevated permissions - https://github.com/masipcat/wireguard-go-docker
-
Unable to run WG on multiple OS's: wireguard RTNETLINK answers: Operation not permitted
I was just curious if it's just me. It seems theres a few posts on various places on the internet on this and the questions are not answered on any of them (EG: https://github.com/masipcat/wireguard-go-docker/issues/19)
What are some alternatives?
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
wg-gen-web - Simple Web based configuration generator for WireGuard
docker-wireguard
subspace - A simple WireGuard VPN server GUI
synology-wireguard - WireGuard support for some Synology NAS drives
wirehole - WireHole is a combination of WireGuard, Pi-hole, and Unbound in a docker-compose project with the intent of enabling users to quickly and easily create a personally managed full or split-tunnel WireGuard VPN with ad blocking capabilities thanks to Pi-hole, and DNS caching, additional privacy options, and upstream providers via Unbound.
gluetun - VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
helmfiles - Comprehensive Distribution of Helmfiles for Kubernetes
nordlynx
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
docker-wireguard-socks-proxy - Expose a WireGuard tunnel as a SOCKS5 proxy
slirp4netns - User-mode networking for unprivileged network namespaces