Port Mapping for VPN Based Containers Reset to Last Container Port Update

[Thomas Edain]

Hey

For a while now every time I update or modify a container which is not redirected through the VPN container, the containers from under the VPN all get the same ports of the container that I've updated/modified. This is problematic as I cannot enable auto-update and I am forced to do manual updates after which I need to go to the VPN Container, modify it and save it, which triggers a forced update of the port mappings of all the related containers reseting them.

Logs are showing this:

After modifying and saving any container not related to the VPN one:

Jul  1 19:44:28 Tower kernel: eth0: renamed from vethb08bd1d
Jul  1 19:44:41 Tower kernel: vethb08bd1d: renamed from eth0
Jul  1 19:44:59 Tower kernel: veth5616f43: renamed from eth0
Jul  1 19:44:59 Tower kernel: docker0: port 4(vethf316952) entered disabled state
Jul  1 19:44:59 Tower kernel: docker0: port 4(vethf316952) entered disabled state
Jul  1 19:44:59 Tower kernel: vethf316952 (unregistering): left allmulticast mode
Jul  1 19:44:59 Tower kernel: vethf316952 (unregistering): left promiscuous mode
Jul  1 19:44:59 Tower kernel: docker0: port 4(vethf316952) entered disabled state
Jul  1 19:45:00 Tower kernel: docker0: port 4(vetha56ab64) entered blocking state
Jul  1 19:45:00 Tower kernel: docker0: port 4(vetha56ab64) entered disabled state
Jul  1 19:45:00 Tower kernel: vetha56ab64: entered allmulticast mode
Jul  1 19:45:00 Tower kernel: vetha56ab64: entered promiscuous mode
Jul  1 19:45:00 Tower kernel: eth0: renamed from vetha930cba
Jul  1 19:45:00 Tower kernel: docker0: port 4(vetha56ab64) entered blocking state
Jul  1 19:45:00 Tower kernel: docker0: port 4(vetha56ab64) entered forwarding state

After modfying and saving VPN Container:

Jul  1 19:51:16 Tower kernel: docker0: port 1(veth2072a9e) entered disabled state
Jul  1 19:51:16 Tower kernel: veth146bb87: renamed from eth0
Jul  1 19:51:16 Tower kernel: docker0: port 1(veth2072a9e) entered disabled state
Jul  1 19:51:16 Tower kernel: veth2072a9e (unregistering): left allmulticast mode
Jul  1 19:51:16 Tower kernel: veth2072a9e (unregistering): left promiscuous mode
Jul  1 19:51:16 Tower kernel: docker0: port 1(veth2072a9e) entered disabled state
Jul  1 19:51:16 Tower kernel: docker0: port 1(vetheed5be8) entered blocking state
Jul  1 19:51:16 Tower kernel: docker0: port 1(vetheed5be8) entered disabled state
Jul  1 19:51:16 Tower kernel: vetheed5be8: entered allmulticast mode
Jul  1 19:51:16 Tower kernel: vetheed5be8: entered promiscuous mode
Jul  1 19:51:16 Tower kernel: eth0: renamed from veth61e4a1b
Jul  1 19:51:16 Tower kernel: docker0: port 1(vetheed5be8) entered blocking state
Jul  1 19:51:16 Tower kernel: docker0: port 1(vetheed5be8) entered forwarding state

Any help is appreciated!

[Mainfrezzer]

Thats a bug since 6.12 was introduced, its only visual. ignoring it is the best you can do. last working version was 6.11.5

Edit: https://forums.unraid.net/bug-reports/stable-releases/6124-dockerpage-shows-bogus-port-mappings-r2632/

Edited July 1 by Mainfrezzer

[Thomas Edain]

Thank you @Mainfrezzer. That seems to be the case.