# Docker Modbus TCP

**URL:** <https://forum.inductiveautomation.com/t/docker-modbus-tcp/52915>\
**Category:** Ignition\
**Created:** [November 10, 2021, 11:27am UTC](https://forum.inductiveautomation.com/t/docker-modbus-tcp/52915 "2021-11-10T11:27:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![helge.rosvik](https://avatars.discourse-cdn.com/v4/letter/h/57b2e6/32.png) [@helge.rosvik](https://forum.inductiveautomation.com/u/helge.rosvik)\
**Post date:** [November 10, 2021, 11:27am UTC](https://forum.inductiveautomation.com/t/docker-modbus-tcp/52915/1 "2021-11-10T11:27:08Z")

</div>

To communicate with Modbus TCP devices, is it necessary to expose port 502 to docker container?

---

<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:** [November 10, 2021, 2:05pm UTC](https://forum.inductiveautomation.com/t/docker-modbus-tcp/52915/2 "2021-11-10T14:05:13Z")

</div>

No, you shouldn’t need to expose/publish anything to make the outbound 502/tcp connections.