did you define that nas folder as /media inside container ?
Thank you for this guide!
As is now possible to directly use yaml in EE without dockge, is it possible to configure app from official catalog to use gluetun?
For example, I have gluetun configured with the compose.yaml provided here running on my truenas server and qbitorrent installed fro the catalog. Is it a way to change the qbitorrent configuration to route the connection by gluetun?
As is now possible to directly use yaml in EE without dockge, is it possible to configure app from official catalog to use gluetun?
As far as I can tell, no. Doing this in a regular docker-compose.yml file requires a line like ânetwork_mode: container:gluetunâ, but there doesnât seem to be a way to add this with the apps in the official catalog. It probably wouldnât be that hard to add, but it hasnât been done for some reason.
For now, Iâm just installing gluetun and qbit using the custom docker-compose functionality in EE, and it mostly works well, except it doesnât start up correctly on reboot and I have to manually restart the containers in sequence. I tried using dockge before, and it worked just as well, but no better because it didnât restart the containers at all on reboot.
1 Like
I have tried to add ânetwork_mode: container:gluetunâ in yml files of the official qbittorrent app but it doesnât work.
So for the time being, I too am using the custom docker-compose functionality
As others have already noted, you canât link to other docker networks using the offical TrueNAS apps, you must use a custom yaml deployment to access these options. There is a github issue open to allow direct binding to a specific IP address configured on the TrueNAS system where I commented that in addtion to that it would be nice to allow the network_mode options for just these situations.
1 Like
568:568 belongs to user âappsâ if i remember correctly, give permissions in datasets perhaps ?
Thanks for the guide! It works perfect for me. If you are like me and have a WireGuard wg.conf file to set up your VPN, Gluetun supports this. You just have to mount it in the right place, as described in gluetun docs (look for wireguard for custom vpn provider).
thanks for guide, i got the app working and tested for the ipleak, it is running with Wireguard and AirVPN. for some reason i am not able to download any files. all my downloads are failing with Status âErroredâ.
config file used:
services:
gluetun:
cap_add:
- NET_ADMIN
container_name: gluetun
devices:
- /dev/net/tun:/dev/net/tun
environment:
- TZ=America/Chicago
- VPN_SERVICE_PROVIDER=custom
- VPN_TYPE=wireguard
- WIREGUARD_ENDPOINT_IP=redacted
- WIREGUARD_ENDPOINT_PORT=51820
- WIREGUARD_PUBLIC_KEY=redacted
- WIREGUARD_PRIVATE_KEY=redacted
- WIREGUARD_PRESHARED_KEY=redacted
- WIREGUARD_ADDRESSES=redacted
- FIREWALL_VPN_INPUT_PORTS=6881
- SERVER_COUNTRIES= #optional
- DNS_ADDRESS= redacted
image: qmcgaw/gluetun:latest
ports:
- 8888:8888/tcp # HTTP proxy
- 8388:8388/tcp # Shadowsocks
- 8388:8388/udp # Shadowsocks
- 8080:8080 #qbittorrent
- 6881:6881 #qbittorrent
- 6881:6881/udp #qbittorrent
restart: unless-stopped
qbittorrent:
container_name: qbittorrent2
depends_on:
- gluetun
environment:
- PUID=568
- PGID=568
- TZ=America/Chicago
- WEBUI_PORT=8080
image: linuxserver/qbittorrent:latest
network_mode: service:gluetun
restart: unless-stopped
volumes:
- /mnt/redacted:/config
- /media:/media
any suggestion to fix this is appreciated.
Thank you
this is resolved, turns out to be an issue with the volume path for /media
@jagadeeps What did you put as your mount path for the media? I have container set to â/mnt/Plugins/Media/mediaâ and qbit downloads to â/media/downloads.â So far all of mine get the same error as you were before and know that it is my path, but not sure what I am doing wrong. Thanks!
here are my storage paths.
I forgot that the â:â was needed, but I got it now. Thanks!
Iâm having a user permission issue, Iâm not sure how to fix it, in the qbitorrent file permissions.
I get this error:
error: Permission denied
In my compose file Iâve got my env set properly and the file location (as far as I can tell):
environment:
- PUID=568
- PGID=568
# edited out others
volumes:
- /mnt/.ix-apps/app_config/qbittorrent:/config
- /mnt/DataStore/share/media/downloads:/media
Iâve validated that I can see the files when I get a shell in the container and navigate to /media.
Checking the user inside the container, I can see that the user and the permissions on /media match:
root@4fa4d9721e21:/# ps -aux | grep /usr/bin/qbit
abc 145 0.6 0.0 72372 39060 ? Ssl 10:57 0:04 /usr/bin/qbittorrent-nox --webui-port=8080 --torrenting-port=6881
root@4fa4d9721e21:/# ls -l | grep media
drwxrwxrwx+ 2 abc abc 3 Mar 16 10:45 media
When I look at my dataset (media/) the permissions seem to be set properly:
Owner: apps
Group: apps
Iâm really not sure what else I can do to troubleshoot. Has anyone any ideas?
Ah, I figured out the issue. Iâm an idiot.
Default download location in qbitorrent was /downloads and Iâd mounted it as /media. Changing it to the correct default location did the trick.
If anyone wants to steal my config, hereâs my protonvpn-based compose files.
I also added a Web UI button on qbittorrent (weirdly, youâll get unauthorized unless you click the URL bar and hit enter, refresh doesnât work).
qbittorrent:
services:
qbittorrent:
container_name: qbittorrent
restart: unless-stopped
environment:
- PUID=568
- PGID=568
- TZ=<TZ HERE>
- WEBUI_PORT=8080
- TORRENTING_PORT=6881
image: lscr.io/linuxserver/qbittorrent:latest
network_mode: container:gluetun
volumes:
- /mnt/.ix-apps/app_config/qbittorrent:/config
- <DATASET PATH HERE>:/downloads
x-portals:
- host: <TRUENAS SCALE IP>
name: Web UI
path: /
port: 8080
scheme: http
and the gluetun compose file for protonvpn:
version: "3"
services:
gluetun:
image: qmcgaw/gluetun
container_name: gluetun
restart: unless-stopped
cap_add:
- NET_ADMIN
ports:
- 8888:8888/tcp # HTTP proxy
- 8388:8388/tcp # Shadowsocks
- 8388:8388/udp # Shadowsocks
- 8080:8080 #qbittorrent
- 6881:6881 #qbittorrent
- 6881:6881/udp #qbittorrent
volumes:
- <YOUR MOUNT HERE>:/gluetun
environment:
- VPN_TYPE=wireguard
- VPN_SERVICE_PROVIDER=protonvpn
- WIREGUARD_PRIVATE_KEY=<PRIVATE KEY>
- WIREGUARD_ADDRESSES=<WIREGUARD ADDRESS>
- WIREGUARD_PUBLIC_KEY=<PUBLIC KEY>
- WIREGUARD_ENDPOINT_IP=<ENDPOINT IP HERE>
This eventually got me to the finish line. I found some other similar write-ups, but this one finally got all the pieces fitted correctly.