I did a search and could not find a similar problem and thought I would try posting it here in General Support. I apologize if this has already been addressed, I just wasn't sure what to search for.

 

I use Gluetun to connect to my VPN (PIA) and then have a few docker containers use Gluetun as the network using  "--net=container:GluetunVPN" in extra parameters and assign the ports in Gluetun instead of the forwarded container template.

 

It all works fine....but after a few days it starts showing IP addresses and port numbers from other running containers. I have a couple of screen shots that show what happens. 

 

Also, even though it shows the wrong IP address and port number when I run "curl ifconfig.io" in the console it shows the IP address of the Gluetun container. So it seems like it is working like it should but showing the wrong network information in the Docker tab. 

 

Finally my questions: Is this a bug? Am I doing something wrong? Is this something to worry about?

 

BTW, if I edit the network in the container template from "none" to "bridge (or anything)" back to "none" the container redeploys and the IP and ports are cleared as expected....but they pick up weird IP and port numbers again after a few days.

 

Thanks for your help

 

 

 

 

 

Hopeful bump for feedback.

I found this post after describing the same issue in a reply on another post.

 

I'm glad to know I'm not the only one. It would be nice to get some support feedback from someone soon.

Did anyone end up figuring this one out? Happened for the first time to me the other day.

Edited June 6, 20242 yr by earthyinsightpuppy
removed unnecessary info

Still no answers....sorry.

what about now? anyone figure this out?

I updated Unraid and started using Folder View 2 and the problem went away.