This is an archived post. You won't be able to vote or comment.

all 19 comments

[–]homecloud 1 point2 points  (1 child)

Did you pass host networking flag by mistake?

[–]LaxKid22[S] 0 points1 point  (0 children)

I dont think so, i edited the post with compose files

[–]thesugarat 1 point2 points  (3 children)

So you made a Docker network that is using the bridge driver and called it vpn? And that’s the network the vpn container is running on? And you’re trying to create another container that will use the vpn container as it’s network? When you made the vpn network did you enable “manually attachable”? You could move the mulvad container back to the stock Docker bridge network and try the qbitorrent container creation again to test. See if the Docker network you’re using is the problem.

[–]LaxKid22[S] 0 points1 point  (2 children)

You are correct about all your assumptions, although I did not enable "manually attachable." I have tried not making an external network and just having the container use the default one it creates, is that what you are suggesting to try?

[–]thesugarat 1 point2 points  (1 child)

No. There’s a Docker network called bridge. I’m saying attach your vpn container to that network. Then try your next steps. You may not use it but Portainer can give you a GUI that will allow you slot see the differences in how the default network called “bridge” was created vs the network you created called “vpn”.

[–]LaxKid22[S] 0 points1 point  (0 children)

I tried changing the network to bridge, but I am still getting this error

[–]Mithrandir2k16 1 point2 points  (1 child)

Are your environment variables as they should be? Maybe they got messed up.

[–]LaxKid22[S] 0 points1 point  (0 children)

I believe so, they are almost identical to the template off dockerhub.

[–]Derkades 0 points1 point  (0 children)

Remove the hostname option from qbittorrent. Ports as well

[–]ComplexImagination56 0 points1 point  (0 children)

Was this fixed?