# Connecting to host TCP/IP server from inside docker container **URL:** \ **Category:** Ignition\ **Created:** [July 9, 2024, 7:32am UTC](https://forum.inductiveautomation.com/t/connecting-to-host-tcp-ip-server-from-inside-docker-container/92942 "2024-07-09T07:32:56Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Patrik\_Olsson\_Bichis](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/patrik_olsson_bichis/32/64787_2.png) [@Patrik\_Olsson\_Bichis](https://forum.inductiveautomation.com/u/Patrik_Olsson_Bichis)\ **Post date:** [July 9, 2024, 7:32am UTC](https://forum.inductiveautomation.com/t/connecting-to-host-tcp-ip-server-from-inside-docker-container/92942/1 "2024-07-09T07:32:56Z")
Hi I'm trying to connect to an TCP/IP server that I'm running on my host computer, I'm using the TCP Driver but the connection is refused. docker run -d -p 9088:8088 -p 9001:9001 -p 9002:9002 --name ignition-edge -v igw-data:/usr/local/bin/ignition/data --pull always inductiveautomation/ignition:latest -n docker-test -a localhost -h 9088 -s 9043 The server is listening on 127.0.0.1 and port 9001. Is there any configuration that I need to do when running it in a docker container that I'm missing? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/2/620e33f5b8ed4484fe5f3798f34dee934eb0cd78.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/0/c0b3aa29679c514679c07a87e7b1b8d8b0c4f1b9.png) ---
**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:** [July 9, 2024, 11:59am UTC](https://forum.inductiveautomation.com/t/connecting-to-host-tcp-ip-server-from-inside-docker-container/92942/2 "2024-07-09T11:59:27Z")
Don't put any mention of port 9001 in your docker command. That is for port mappings from host to container, and will interfere with traffic from container to host. Then, use your host's **name** instead of localhost from inside the container. ---
**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:** [July 10, 2024, 2:49am UTC](https://forum.inductiveautomation.com/t/connecting-to-host-tcp-ip-server-from-inside-docker-container/92942/3 "2024-07-10T02:49:55Z")
Here are a couple useful references for you: > [@Ignition Docker with sql database](https://forum.inductiveautomation.com/t/ignition-docker-with-sql-database/50571/7): > > I'll also augment that as of Docker Engine 20.10, you can also use host.docker.internal mapping on Linux (where it was previously only available on Docker Desktop). You do have to add an extra\_hosts mapping to your container definition though, such as: docker run ... --add-host "host.docker.internal:host-gateway" ... ... or in your Compose YAML: services: gateway: ... extra\_hosts: - "host.docker.internal:host-gateway" .... With this, the hostname host.docker.internal wil… > **[Explore networking features on Docker Desktop](https://docs.docker.com/desktop/networking/#i-want-to-connect-from-a-container-to-a-service-on-the-host)** > > Understand how networking works on Docker Desktop and see the known limitations ---
**Author:** ![Patrik\_Olsson\_Bichis](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/patrik_olsson_bichis/32/64787_2.png) [@Patrik\_Olsson\_Bichis](https://forum.inductiveautomation.com/u/Patrik_Olsson_Bichis)\ **Post date:** [July 10, 2024, 4:50am UTC](https://forum.inductiveautomation.com/t/connecting-to-host-tcp-ip-server-from-inside-docker-container/92942/4 "2024-07-10T04:50:10Z")
Thank you, when using host.docker.internal everything worked as expected. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/5/55abe1002e64a5b5335490043ef9f716130e23bf.png)