Accessing Docker Services/Network on Mac Host LAN VPN

General
, ,
21

This behavior is not caused by Docker Desktop itself, but rather an effect of what qbittorent does.

Can you check if the network of the utiliy vm is actually 192.168.65.0/24, as configured in the service’s environment variable VPN_LAN_NETWORK=192.168.65.0/24.

It is clear now that the qbittorent container controls the firewall of the utility vm (before I always wondered why you pasted iptables rules). Of course, it can not control anything outside the utility vm.

Worst case, you will need to wait for someone who actually uses qbittorent with Docker Desktop, or even better find the qbittorent support channel, as it’s more likely to find qbittorent users that try to run it on Docker Desktop, than Docker Desktop users here in the forum that try to run qbittorent in it.

Docker Desktop is a developer tool, it is not designed as a 24/7 container runtime. If you own a nas, you would be better off to run those containers on a nas.

22

That’s what docker network settings reports yes. Though the iptables or something also reference (an internal?) 172….

Yep, probably awaiting a macOS guru. I don’t own a NAS. This all runs on an m1 Mac mini. Ok, I may venture down the qbit forums (?) path looking for those who run similarly. Thanks!

23

You forgot address to this part. It is the most relevant part of the post, because if the network cidr for your utility vm is different, it would explain the behavior.

Update: now that I read you post twice: you already confirmed it.

Please keep us posted, if you find the answer so others with the same problem benefit from your experience!

24

I’m really curious why this
I’m running this version and the below command works just fine:

docker run --rm -p 8080:8080 
  -e VPN_ENABLED=true  
  -e VPN_LAN_NETWORK=192.168.65.0/24 
  -v ./qbit:/config 
  --cap-add=NET_ADMIN 
  --sysctl="net.ipv6.conf.all.disable_ipv6=1" 
  --sysctl="net.ipv4.conf.all.src_valid_mark=1"
ghcr.io/hotio/qbittorrent:release

Was reported as working by the author of the image but my severely reduced compose did not…
Just noticed.. firewall possibly?? Though I don’t see a benefit in removing that overall.

Will keep you posted :+1::sign_of_the_horns:

25

I am surprised the command has no details for the vpn connection. How is a container crated like that supposed to create the same firewall rules, it creates after a vpn connection is established?

Just out of curiosity: can you check if access from outside still works, if you run it without the VPN_LAN_NETWORK variable?

26

I asked him about missing stuff there, simple answer, if not explicitly set any variable will use defaults. Like firewall setting and the location of a wg0.conf.

27

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.