Open ostracizado opened 1 year ago
Hello,
I just figured this out myself after quite a bit of research. Will provide a explanation with extra additional information afterwards for anyone else reading this 😄
This will cover binhex faq for vpn Q24, Q25 and Q26 which as you know deals with connecting other containers through binhex/arch-delugevpn
Edit: I'm unsure how to do this through Portainer GUI manually. The below is using Portainer
Stacks. You can copy and paste docker compose files and docker compose env files under the Stacks section in Portainer
You are correct Extra Parameters
is just for unRAID. For docker CLI
/ docker compose
and Portainer
(which as you know is a GUI for docker CLI/ docker compose); you will need to add a --network
(docker cli) / netowrk_mode
(docker compose)
Sample Docker compose - note this is only a sample with the parts you need to make this work. it is not the full docker compose
#Note: This is a separate docker compose file for binhex/arch-delugevpn. More information in additional information section
services:
delugevpn:
image: binhex/arch-delugevpn:latest
container_name: delugevpn
environment:
- VPN_INPUT_PORTS=${FlexgetPort}
ports:
# ports of other applications that need VPN
#Note: I use file env vars to ensure the ports are all the same and there is no typo
- ${FlexgetPort}:${FlexgetPort}
#env var file for docker compose for binhex/arch-delugevpn. Note this is an example port
FlexgetPort=8989
#Note: This is a separate docker compose file. I will only be using Flexget name to display the connection between the two docker compose files
services:
flexget:
container_name: flexget
#this is equivalent to unRAID "Extra Parameters" "--net=container:<vpn container name>"
network_mode: container:delugevpn
#this comment is to show that no ports are needed. will pass through delugevpn VPN_INPUT_PORTS.
#ports:
# - '8989:8989'
binhex/arch-delugevpn
is separate from the other applications that need VPN is because binhex/arch-delugevpn
needs to have fully started up before any other container that relies on it
binhex/arch-delugevpn
started before I start any other service that relies on itunRAID
, docker CLI
and docker compose
which includes Portainer
Extra Parameters
is needed in unRAID because that is the specific way to add any additional fields like network and ports to the docker container--net
is an older parameter to add a network to the docker container--network
--network=container:<container_name>
network_mode
as shown in the example network_mode: container:<container_name>
Hope that helps!
I'm having some problems trying to connect flexget to delugevpn. (Error 111)
Searching through the documentation I found this:
The "Extra Parameters" where I could add "--net=container:", I believe, are applied to unRAID. In Portainer what would be the best approach?
Could I add a new ENV as "ExtraParams=--net=container:binhex-delugevpn"?