If there are anyone here that have the time the docker image I’m trying to run is: dyonr/qbittorrentvpn
The image is basically running qBittorrent through a VPN client, but the readme is written on the assumption that the image is configured and started via terminal so I’m guessing I just missed something that needs to be configured.
Before it crashes I can tell that the VPN connection is established. I can even ping local machines as well so the routing between the VPN and the local network is working too but I can’t see that the instance ever gets an IP address neither via shell commands or in the TrueNAS app management UI.
I assume there are logs somewhere, but where do I find them?
Slightly different image you are running @tontze, but I just want something that works so I might give this a go. Given the file you are showing me I assume you are using the yaml file option when setting it up and not the GUI configurator or is this some kind of summary view Truenas provides of GUI your configurator settings?
So after fiddling about a bit I managed to get the binhex/arch-qbittorrentvpn container running with an openvpn configuration. Would like to use wireguard, but to be honest it matters very little.
Now I’m getting stopped at some point due to permissions:
..
2024-12-12 16:05:40.802503 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2024-12-12 16:05:40.822775 [info] ENABLE_SOCKS defined as 'yes'
2024-12-12 16:05:40.844320 [info] ENABLE_PRIVOXY defined as 'yes'
2024-12-12 16:05:40.863456 [info] SOCKS_USER defined as 'admin'
2024-12-12 16:05:40.882061 [info] SOCKS_PASS defined as 'socks'
2024-12-12 16:05:40.901117 [info] WEBUI_PORT defined as '8080'
2024-12-12 16:05:46.010489 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
chmod: changing permissions of '/config/supervisord.log': Operation not permitted
For the sake of convenience the folders mounted here are share via SMB, but i have given the apps user full control via the Set ACL feature in TrueNAS (recurisvely for the dataset). Should that not be enough?
It was indeed a permission issue. I had set up the folders with access in accordance with the plex app preset, but I had not set the correct PUID and PGID in the YAML file. When i fixed that it started working as expected.