# Docker Instance Sign-in **URL:** \ **Category:** General Discussion\ **Tags:** ignition81\ **Created:** [February 7, 2024, 11:48am UTC](https://forum.inductiveautomation.com/t/docker-instance-sign-in/85360 "2024-02-07T11:48:18Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Darren\_Steele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/darren_steele/32/55624_2.png) [@Darren\_Steele](https://forum.inductiveautomation.com/u/Darren_Steele)\ **Post date:** [February 7, 2024, 11:48am UTC](https://forum.inductiveautomation.com/t/docker-instance-sign-in/85360/1 "2024-02-07T11:48:18Z")
I have several ignition gateways running on the same linux machine in their own docker containers. Everything is working well and I can connect to the different ports of the same IP address and connect to each individual gateway. The only oddity is that when I sign into the gateway in one instance then the user in another instance automatically gets logged out. It's not a massive deal but I'm confused about why ignition gateways running in their own container are interfering with each other. Anybody got any suggestions? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 7, 2024, 1:20pm UTC](https://forum.inductiveautomation.com/t/docker-instance-sign-in/85360/2 "2024-02-07T13:20:21Z")
Same hostname, same cookie, unfortunately. > [@Docker: Why does logging in on one Ignition instance cause log out on other Ignition instances?](https://forum.inductiveautomation.com/t/docker-why-does-logging-in-on-one-ignition-instance-cause-log-out-on-other-ignition-instances/78839/4): > > I don't think this is Chrome-specific, but rather how [HTTP cookies are specified](https://www.rfc-editor.org/rfc/rfc6265). In particular: Similarly, cookies for a given host are shared across all the ports on that host, even though the usual "same-origin policy" used by web browsers isolates content retrieved via different ports. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 7, 2024, 1:31pm UTC](https://forum.inductiveautomation.com/t/docker-instance-sign-in/85360/3 "2024-02-07T13:31:01Z")
You can make unique hostnames in `/etc/hosts` that all point at `127.0.0.1` if you don't want to stand up any special DNS tools. ---
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [February 7, 2024, 2:17pm UTC](https://forum.inductiveautomation.com/t/docker-instance-sign-in/85360/4 "2024-02-07T14:17:28Z")
In one of the Docker training presentations, I remember @kcollins had a domain that would just resolve every name you threw at it as 127.0.0.1 for convenience. I can't find it right now. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 7, 2024, 2:18pm UTC](https://forum.inductiveautomation.com/t/docker-instance-sign-in/85360/5 "2024-02-07T14:18:15Z")
It may be the one he mentions in the post I linked, [sslip.io](http://sslip.io). ---
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [February 7, 2024, 2:21pm UTC](https://forum.inductiveautomation.com/t/docker-instance-sign-in/85360/6 "2024-02-07T14:21:07Z")
It was the other one earlier in that thread: `*.localtest.me` 😛 ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [February 7, 2024, 2:29pm UTC](https://forum.inductiveautomation.com/t/docker-instance-sign-in/85360/7 "2024-02-07T14:29:03Z")
I've found more and more systems offering native local resolution of `*.localhost` names, so that might be an option too, albeit possibly less universal. ---
**Author:** ![Darren\_Steele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/darren_steele/32/55624_2.png) [@Darren\_Steele](https://forum.inductiveautomation.com/u/Darren_Steele)\ **Post date:** [February 7, 2024, 4:55pm UTC](https://forum.inductiveautomation.com/t/docker-instance-sign-in/85360/8 "2024-02-07T16:55:38Z")
Thanks Kevin - really was that simple huh??? I've been staring at the docker\_compose.yml file for ages hahahaha