Easy. There are several Bittorrent dockers that have VPN capability built in. I am currently using dyonr/qbittorrentvpn, but there are others.
Easy. There are several Bittorrent dockers that have VPN capability built in. I am currently using dyonr/qbittorrentvpn, but there are others.
Thank you. So, I shouldn't need an overall VPN and just let a docker handle it?
Thank you. So, I shouldn't need an overall VPN and just let a docker handle it?
This is what I have been doing for many years.
So I've been thinking about this for a while.
Today I have a full VM, a desktop that basically runs just a webbroweser and qbittorrent and my VPN providers desktop client.
It works well and all that but I'd like to move that stuff to a container, using qbittorrentvpn would solve most of it but not the webbroser stuff that I use to get the torrent files or magnet links... is there a way to solve that ?
How do you solve that?
For example, you can run firefox in a container: https://github.com/jlesage/docker-firefox
Heyyy, that was cool 
Know if/how you can route traffic from one container to the other - so that ff container uses vpn/qbt container OR if there is someone who have made all of this in one?
Easy. There are several Bittorrent dockers that have VPN capability built in. I am currently using dyonr/qbittorrentvpn, but there are others.
Are you running Wireguard in a different location? Like a service or internally or is it all in that docker?
The dyonr/qbittorrentvpn image has the VPN built into it. Wireguard or OpenVPN can be used with it. I subscribe to Torguard.net for VPN and Proxy services.
Heyyy, that was cool
Know if/how you can route traffic from one container to the other - so that ff container uses vpn/qbt container OR if there is someone who have made all of this in one?
To have the FF container use the qbt/VPN network:
1) Add a network_mode: statement to the FF container that points to the qbt/VPN container and remove the port statement from the FF container.
2) Add the port statement that was removed from the FF container to the qbt/VPN container.
Restart both containers.
Display MoreTo have the FF container use the qbt/VPN network:
1) Add a network_mode: statement to the FF container that points to the qbt/VPN container and remove the port statement from the FF container.
2) Add the port statement that was removed from the FF container to the qbt/VPN container.
Restart both containers.
Do you recognize this?
-1 }">[#] ip link add wg0 type wireguard
-1 }">RTNETLINK answers: Operation not permitted
-1 }">Unable to access interface: Operation not permitted
-1 }">[#] ip link delete dev wg0
-1 }">Cannot find device "wg0"Do you recognize this?
Code-1 }">[#] ip link add wg0 type wireguard -1 }">RTNETLINK answers: Operation not permitted -1 }">Unable to access interface: Operation not permitted -1 }">[#] ip link delete dev wg0 -1 }">Cannot find device "wg0"
No.
No.
Had to add
cap_add:
- NET_ADMIN
Now i have a new issue
2022-11-05 07:28:06.628299 [WARNING] ENABLE_SSL is set to '', SSL is not enabled. This could cause issues with logging if other apps use the same Cookie name (SID).
2022-11-05 07:28:06.639058 [WARNING] Removing the SSL configuration from the config file...
2022-11-05 07:28:06.651051 [INFO] A group with PGID 100 already exists in /etc/group within this container, nothing to do.
2022-11-05 07:28:06.662442 [INFO] An user with PUID 998 already exists within this container, nothing to do.
2022-11-05 07:28:06.673036 [WARNING] UMASK not defined (via -e UMASK), defaulting to '002'
2022-11-05 07:28:06.683599 [INFO] Starting qBittorrent daemon...
Logging to /config/qBittorrent/data/logs/qbittorrent.log.
2022-11-05 07:28:07.698332 [INFO] Started qBittorrent daemon successfully...
2022-11-05 07:28:07.709912 [INFO] qBittorrent PID: 202
2022-11-05 07:28:07.720931 [INFO] HEALTH_CHECK_HOST is not set. For now using default host one.one.one.one
2022-11-05 07:28:07.731468 [INFO] HEALTH_CHECK_INTERVAL is not set. For now using default interval of 300
2022-11-05 07:28:07.742177 [INFO] HEALTH_CHECK_SILENT is not set. Because this variable is not set, it will be supressed by default
2022-11-05 07:28:07.752836 [WARNING] RESTART_CONTAINER not defined,(via -e RESTART_CONTAINER), defaulting to 'yes'
2022-11-05 07:28:07.763521 [INFO] HEALTH_CHECK_AMOUNT is not set. For now using default interval of 1
2022-11-05 07:28:07.774050 [INFO] HEALTH_CHECK_AMOUNT is set to 1
2022-11-05 07:28:35.811866 [ERROR] Network is possibly down.
2022-11-05 07:28:36.823145 [INFO] Restarting container.You will not get any meaningful help until you provide either the docker run command or the docker compose file you are using.
You will not get any meaningful help until you provide either the docker run command or the docker compose file you are using.
Apologies
---
version: "2"
services:
qbittorrentvpn:
image: dyonr/qbittorrentvpn
container_name: movies-qbitvpn
environment:
- VPN_ENABLED=yes
- VPN_TYPE=wireguard
- PUID=998 #optional
- PGID=100 #optional
- LAN_NETWORK=192.168.1.0/24
- NAME_SERVERS=8.8.8.8,8.8.4.4
ports:
- 8081:8080
- 8999:8999
- 8999:8999/udp
volumes:
- /srv/dev-disk-by-uuid-579c6cde-d8b4-4895-a757-683c5b9bf007/nvme1/config/qbitmoviesvpn:/config
- /Fileserver/Fileserver/downloads/movies:/downloads
restart: unless-stopped
cap_add:
- NET_ADMINDifficult to evaluate your posted Docker Compose file because the indents are not shown here. You may actually have them correct, but if not an improperly indented file will fail miserably every time. Please use code boxes when posting compose files. Having said that I'll comment about the contents themselves where a comment is needed.
- PUID=998: 998 is the OMV admin user ID and not a good choice for running dockers. This alone will not break a container or prevent it from running but it will complicate other things later on because every file and folder the container creates will be owned by that user, and it may be difficult to manage these files or your client programs that need to read these files might not have the needed permission. I know, you probably found the suggestion to set PUID=998 on a web page or YouTube video, but that doesn't make it right. You should create a new user on your system for running containers. A suggested username would be your first name, all lower case. The newly created user should belong to the docker, ssh, sudo, and users groups.
ports: - 8081:8080 This is probably the gotcha that is breaking things for you. I have never been able to get this image to run with different port numbers on either side of the colon. They both have to be the same, and if I recall correctly, even changing them to something other than 8080 will not work. I had the same problem with the marcusmcnugen/qbittorrent image. I strongly suggest using 8080:8080 here and if this is in conflict with another service or container on your system, change that one.
The rest of the file looks OK to me, so long as you don't have any typos in the volumes. Personally, I avoid using upper case in filenames because the filesystem is case sensitive and if you do use mixed case names you have to be completely accurate with them everywhere.
Good luck.
Edit: Did you generate a wg0.conf file and place it in this directory?
/srv/dev-disk-by-uuid-579c6cde-d8b4-4895-a757-683c5b9bf007/nvme1/config/qbitmoviesvpn/wiregaurd/
Display MoreDifficult to evaluate your posted Docker Compose file because the indents are not shown here. You may actually have them correct, but if not an improperly indented file will fail miserably every time. Please use code boxes when posting compose files. Having said that I'll comment about the contents themselves where a comment is needed.
- PUID=998: 998 is the OMV admin user ID and not a good choice for running dockers. This alone will not break a container or prevent it from running but it will complicate other things later on because every file and folder the container creates will be owned by that user, and it may be difficult to manage these files or your client programs that need to read these files might not have the needed permission. I know, you probably found the suggestion to set PUID=998 on a web page or YouTube video, but that doesn't make it right. You should create a new user on your system for running containers. A suggested username would be your first name, all lower case. The newly created user should belong to the docker, ssh, sudo, and users groups.
ports: - 8081:8080 This is probably the gotcha that is breaking things for you. I have never been able to get this image to run with different port numbers on either side of the colon. They both have to be the same, and if I recall correctly, even changing them to something other than 8080 will not work. I had the same problem with the marcusmcnugen/qbittorrent image. I strongly suggest using 8080:8080 here and if this is in conflict with another service or container on your system, change that one.
The rest of the file looks OK to me, so long as you don't have any typos in the volumes. Personally, I avoid using upper case in filenames because the filesystem is case sensitive and if you do use mixed case names you have to be completely accurate with them everywhere.
Good luck.
Edit: Did you generate a wg0.conf file and place it in this directory?
/srv/dev-disk-by-uuid-579c6cde-d8b4-4895-a757-683c5b9bf007/nvme1/config/qbitmoviesvpn/wiregaurd/
I changed post and posted it in code format.
Change the port to 8080 again
Still getting network is possibly down.
I'll fix the User issues later once I get time and not under the gun to get this working.
Don’t have an account yet? Register yourself now and be a part of our community!
