# Gateway Memory Not Matching Config on Docker Container

**URL:** <https://forum.inductiveautomation.com/t/gateway-memory-not-matching-config-on-docker-container/98631>\
**Category:** Ignition\
**Tags:** docker\
**Created:** [November 14, 2024, 7:53pm UTC](https://forum.inductiveautomation.com/t/gateway-memory-not-matching-config-on-docker-container/98631 "2024-11-14T19:53:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nick\_Kienzle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nick_kienzle/32/42548_2.png) [@Nick\_Kienzle](https://forum.inductiveautomation.com/u/Nick_Kienzle)\
**Post date:** [November 14, 2024, 7:53pm UTC](https://forum.inductiveautomation.com/t/gateway-memory-not-matching-config-on-docker-container/98631/1 "2024-11-14T19:53:08Z")

</div>

I'm running a docker container (official image inductiveautomation/ignition:8.1.43) on an ubuntu vm running on a proxmox server. The gateway says it's configured for 1 GB max memory, but the ignition.conf file is showing that wrapper.java.maxmemory=8192. I have seen another forum post somewhat similar, but not quite the same here [Where is the ignition.conf file in a Docker container? - #8 by ataya](https://forum.inductiveautomation.com/t/where-is-the-ignition-conf-file-in-a-docker-container/50303/8)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/e/4e61b78a60ca383c37fbdbc8c2d72d38aeb7ba0a.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/0/10681dc2ecdb744318eccfc0aa1292b40209c2d1.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 14, 2024, 8:04pm UTC](https://forum.inductiveautomation.com/t/gateway-memory-not-matching-config-on-docker-container/98631/2 "2024-11-14T20:04:05Z")

</div>

What's the actual run command for the container? As the other thread you linked mentioned, 'runtime' overrides of the ignition.conf file are possible when running within Docker.

---

<div class="post-metadata">

**Author:** ![Nick\_Kienzle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nick_kienzle/32/42548_2.png) [@Nick\_Kienzle](https://forum.inductiveautomation.com/u/Nick_Kienzle)\
**Post date:** [November 19, 2024, 1:40pm UTC](https://forum.inductiveautomation.com/t/gateway-memory-not-matching-config-on-docker-container/98631/3 "2024-11-19T13:40:26Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/d/6d52a2d480aa4ec83f746abff0f5ffa2287dda86.png)  
The -m argument was increased (not by myself) by adding a zero to it and it still shows as 1 GB on the gateway.

---

<div class="post-metadata">

**Author:** ![Nick\_Kienzle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nick_kienzle/32/42548_2.png) [@Nick\_Kienzle](https://forum.inductiveautomation.com/u/Nick_Kienzle)\
**Post date:** [November 21, 2024, 1:48pm UTC](https://forum.inductiveautomation.com/t/gateway-memory-not-matching-config-on-docker-container/98631/4 "2024-11-21T13:48:27Z")

</div>

Had to restart the containers and it took the change. Consider this closed.