michielvv
Members
-
Joined
-
Last visited
Solutions
-
michielvv's post in Update containers with custom network fails was marked as the answerSolved all of this: bottom line was that i implemented the wrong way of getting dockers to use the vpn docker's network instead of their own:
1. I made a custom network via the command line pointing to the VPN docker
2. in each of the docker's pull down lists I selected this network to use.
This causes problems when updating (custom network does not seem to be refreshed with the new docker ID of the VPN docker) and portmapping problems somehow.
Instead, I should've done the following:
1. for each docker, set network to 'none'
2. for each docker, add extra parameter "--net=container:[your vpn dockername - only lowercase allowed!!!]"
And bingo: updating the vpn dockers refreshes the relying dockers automatically and portmapping is transparently working without errors. super!