Getting signed out of GW webpage when hosting multiple Gateways w/Docker

[Cade_Allen]

Hi, I’m running multiple Gateways with Docker on my local computer. I have each Gateway mapped to unique ports, but I’ve noticed that when I sign into one Gateway webpage, it signs me out of the other. Additionally, I have to sign in twice to gain access to the webpage. Any thoughts on why this could be happening?

[Kevin.Herron]

Multiple docker instances on the same host share the same connection

More on this behavior here: It's a function of the webserver not isolating the session authentication cookies per host:ip - only per host. There's a workaround mentioned there, but I wouldn't necessarily recommend it unless you really know what you're doing. If you're developing entirely on the local machine, there should be internal IPs for each container that are unique - something like 172.17.0.X. You can access whatever port on that internal IP, regardless of what the container is set to …

I think this changed in 8.3 though?

[Kevin.Herron]

Actually it may not have changed... I think I was using different hostnames as well as ports when I was in this situation recently.

[Cade_Allen]

Looking at that thread, it looks like I need to access the gateways using the internal container IP addresses?

I tried this and it doesn’t seem like those IPs are exposed to my host. I’m new to Docker - do I need to change the network interface setup to expose those?

Using Docker Desktop on Windows, I can’t ping the container IPs from my host.

[paul-griffith]

Supposed to be fixed as of 8.3.2 - independent gateway names even on the same host will get unique cookies.