amoney

Any pointers to how to fix the following issue when using macvlan network? Cannot open up the UI, telnet to port 8080 works fine. Running on Synology. I have various containes using this network so i know the network setup is working. When i run the qbittorrentvpn container using bridge network it works perferct. So the only 2 changes in how i start the container is specifying the network i want to attach to and ip address. Inside the container it shows its listening to tcp6 which is interesting as IPv6 is not enabled on my docker host. So curious if this it the underlying cause [root@3f26ea402906 /]# netstat -nltp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 192.168.1.240:13392 0.0.0.0:* LISTEN 454/qbittorrent-nox tcp 0 0 10.8.0.9:13392 0.0.0.0:* LISTEN 454/qbittorrent-nox tcp 0 0 127.0.0.1:13392 0.0.0.0:* LISTEN 454/qbittorrent-nox tcp 0 0 127.0.0.11:33496 0.0.0.0:* LISTEN - tcp6 0 0 :::8080 :::* LISTEN 454/qbittorrent-nox [root@3f26ea402906 /]# Sorry for the repeat post. Trying again to see if folks have suggestions on how i can get this to work. Edit: Ah looks like i found a post stating macvlan is not supported in the image. Guess i have to explore other options.

I had no issues using this image when using bridge network with docker. Just cant get it to work with macvlan.

Need some help setting up a docker contantainer with macvlan network. My google fu has failed me so far. Using image binhex/arch-qbittorrentvpn:4ce38f56424c I am running on Synology. I had a container running via bridge network just fine. I am running a vpn client on my router to route all outgoing traffic through a VPN. Now since i have a vpn client running my qBittorrent container is doing a multi hop in some sense. I wanted to see if i can avoid that. So i decided to set up teh container using macvlan. What is werid is i cannot open up the UI. I have confirmed i can telnet to port 8080 from a machine other than the docker host and it connects. Confirmed it by shutting down the container and telnet fails. So i know i can reach the container using the macvlan network. However when i make a curl call it keeps getting curl: (56) Recv failure: Connection reset by peer docker macvlan network is setup as docker network create -d macvlan --subnet=192.168.1.0/24 --ip-range=192.168.1.240/28 --gateway=192.168.1.1 -o parent=eth1 macvlan Here is how i started the container sudo docker run -d \ --privileged=true \ --network macvlan \ --ip 192.168.1.241 \ -p 13392:13392 \ -p 13392:13392/udp \ -p 8080:8080 \ -p 8118:8118 \ --name=qbittorrent \ -v /volume1/htpc:/htpc \ -v /volume1/docker/qbittorrent:/config \ -v /etc/localtime:/etc/localtime:ro \ -e VPN_ENABLED=yes \ -e VPN_PROV=mullvad \ -e VPN_USER=DELETED \ -e VPN_PASS=DELETED \ -e VPN_OPTIONS='--pull-filter ignore ifconfig-ipv6 --pull-filter ignore route-ipv6 --inactive 3600 --ping 10 --ping-exit 60 --mute-replay-warnings' \ -e ENABLE_PRIVOXY=no \ -e LAN_NETWORK=192.168.1.0/24 \ -e NAME_SERVERS=10.8.0.1,1.1.1.1,1.0.0.1 \ -e DEBUG=true \ -e WEBUI_PORT=8080 \ -e UMASK=022 \ -e PUID=DELETED \ -e PGID=DELETED \ --restart=unless-stopped \ binhex/arch-qbittorrentvpn:latest netstat from within the container shows [root@3f26ea402906 /]# netstat -nltp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 192.168.1.240:13392 0.0.0.0:* LISTEN 454/qbittorrent-nox tcp 0 0 10.8.0.9:13392 0.0.0.0:* LISTEN 454/qbittorrent-nox tcp 0 0 127.0.0.1:13392 0.0.0.0:* LISTEN 454/qbittorrent-nox tcp 0 0 127.0.0.11:33496 0.0.0.0:* LISTEN - tcp6 0 0 :::8080 :::* LISTEN 454/qbittorrent-nox [root@3f26ea402906 /]# Any one have any pointers as to what could be happening here? In order to confirm my setup i did the haugene-tranmission setup with macvlan and it is up and running without any issues. So i feel farily confident that my macvlan setup is working correctly.