# Ignition docker image question

**URL:** <https://forum.inductiveautomation.com/t/ignition-docker-image-question/73251>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 4, 2023, 12:10pm UTC](https://forum.inductiveautomation.com/t/ignition-docker-image-question/73251 "2023-05-04T12:10:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pgmo](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@pgmo](https://forum.inductiveautomation.com/u/pgmo)\
**Post date:** [May 4, 2023, 12:10pm UTC](https://forum.inductiveautomation.com/t/ignition-docker-image-question/73251/1 "2023-05-04T12:10:12Z")

</div>

To be honest I'm no docker specialist, just a user for convenience. I cannot find an answer to the purpose of these flags

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/0/304da0850bd14fe06ec017344809b3ad8f9f9866.png)

at the end of the **docker run** command. As I can see, just by adding the `-p 8088:8088` flag to publish the listening Ignition port I can manage to reach the gateway from my host: so why should I add `-a .... -h ..... -s ......`?  
Thanks in advance, regards

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [May 4, 2023, 1:30pm UTC](https://forum.inductiveautomation.com/t/ignition-docker-image-question/73251/2 "2023-05-04T13:30:19Z")

</div>

Hello pgmo,

Those arguments are for specifying the address and ports for public use. The explanation of the docker runtime arguments can be found in the User Manual [here](https://docs.inductiveautomation.com/display/DOC81/Docker+Image#DockerImage-RuntimeArguments) and specifics on those web server settings can be found [here](https://docs.inductiveautomation.com/display/DOC81/Web+Server+Settings#WebServerSettings-PublicHTTPAddresssettings).

Hope those resources help clear up any confusion.

---

<div class="post-metadata">

**Author:** ![pgmo](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@pgmo](https://forum.inductiveautomation.com/u/pgmo)\
**Post date:** [May 4, 2023, 2:12pm UTC](https://forum.inductiveautomation.com/t/ignition-docker-image-question/73251/3 "2023-05-04T14:12:12Z")

</div>

Hallo @avaughn ,thanks for your answer. I've read already the docs, but since the Ignition container runs as expected even if I don't set those flags, I found no use for that. Therefore I was asking for any hints.  
Thanks, regards

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [May 4, 2023, 2:33pm UTC](https://forum.inductiveautomation.com/t/ignition-docker-image-question/73251/4 "2023-05-04T14:33:08Z")

</div>

If your gateway doesn't need to be publicly accessed outside your network then they're not needed, just available as an option. I've personally never used those arguments when running Ignition in Docker.

---

<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:** [May 8, 2023, 2:48pm UTC](https://forum.inductiveautomation.com/t/ignition-docker-image-question/73251/5 "2023-05-08T14:48:19Z")

</div>

In almost all cases, the gateway will use relative redirects which means that things normally work without those settings. But there are a _few_ cases where that isn't the case, and being explicit with the public address settings mitigates those.