I run more than one ignition container on the same host, binding the ports 8088 and 8043 to different couples for each instance and it’s really cool, because in a while I can set up the gateway and work with several designers at the same time.
Actually I’m not a docker expert and probably I miss or I misunderstand some networking concepts, but I cannot manage to isolate the gateway page for those instances: after I logged into the page localhost:80xx I log into the page localhost:80yy, then I go back to localhost:80xx and I have to login again, and so on, back and forth I have to log in any time i browse a different gateway page
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 expose.
Thank you PGriffith!
Your suggestion led me to a very easy solution (tested and working )
I edited my hosts file and added the following lines:
127.0.0.1 ignition.87
127.0.0.1 ignition.90
Now I can log in to http://ignition.87:8087/ and to http://ignition.89:8089/ at the same time without interference.
All I needed is a pool of hostnames pointing at my local IP