# Connect docker with Kepware

**URL:** <https://forum.inductiveautomation.com/t/connect-docker-with-kepware/64426>\
**Category:** Ignition\
**Tags:** docker\
**Created:** [September 23, 2022, 3:10pm UTC](https://forum.inductiveautomation.com/t/connect-docker-with-kepware/64426 "2022-09-23T15:10:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kartik\_I](https://avatars.discourse-cdn.com/v4/letter/k/8c91f0/32.png) [@Kartik\_I](https://forum.inductiveautomation.com/u/Kartik_I)\
**Post date:** [September 23, 2022, 3:10pm UTC](https://forum.inductiveautomation.com/t/connect-docker-with-kepware/64426/1 "2022-09-23T15:10:57Z")

</div>

Hello.

I am trying to connect Kepware Server with Igntion. I am using ignition in docker and I am getting the error(attached image). Can anyone help me out with this issue. The Kepware is installed local machine.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/2/32f30ef96e66514080528fb4658458dc61f4282f.png)

Thanks,  
Kartik

---

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [September 23, 2022, 3:50pm UTC](https://forum.inductiveautomation.com/t/connect-docker-with-kepware/64426/2 "2022-09-23T15:50:41Z")

</div>

You could try reaching out to the docker host at: `host.docker.internal` instead of that IP address.

opc.tcp://host.docker.internal:49320

---

<div class="post-metadata">

**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:** [September 23, 2022, 6:17pm UTC](https://forum.inductiveautomation.com/t/connect-docker-with-kepware/64426/3 "2022-09-23T18:17:09Z")

</div>

I’ll also mention [this thread](https://forum.inductiveautomation.com/t/ignition-gateway-with-docker-connect-to-kepware/53090/2) which seeks a similar goal. Keep in mind [for the future] that `host.docker.internal` will only work on Docker Desktop and isn’t automagically available using just Docker Engine on Linux. See [this reference from Docker docs](https://docs.docker.com/desktop/networking/#i-want-to-connect-from-a-container-to-a-service-on-the-host) for more information. But if you’re running KEPServerEx (thus you’re probably using Docker Desktop for Windows), you should be good.

Other thing I’ll mention is that you can pass in custom hostname-\>ip mappings to your container run configuration that might be helpful in certain situations (where you want to use a specific name for the OPC-UA address). See the [`--add-host`](https://docs.docker.com/engine/reference/commandline/run/) guidance for `docker run` or [`extra_hosts`](https://github.com/compose-spec/compose-spec/blob/master/spec.md#extra_hosts) key for Compose. Unfortunately this doesn’t let you alias the name, so you’d have to actually lookup what `host.docker.internal` points to and use that IP (hint: it is _usually_ `192.168.65.2` to access your host from within a container).

---

<div class="post-metadata">

**Author:** ![Kartik\_I](https://avatars.discourse-cdn.com/v4/letter/k/8c91f0/32.png) [@Kartik\_I](https://forum.inductiveautomation.com/u/Kartik_I)\
**Post date:** [September 24, 2022, 3:10am UTC](https://forum.inductiveautomation.com/t/connect-docker-with-kepware/64426/4 "2022-09-24T03:10:18Z")

</div>

thanks @kgamble it helped.