# Where is the ignition.conf file in a Docker container? **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [August 25, 2021, 11:03pm UTC](https://forum.inductiveautomation.com/t/where-is-the-ignition-conf-file-in-a-docker-container/50303 "2021-08-25T23:03:51Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![ataya](https://avatars.discourse-cdn.com/v4/letter/a/f9ae1b/32.png) [@ataya](https://forum.inductiveautomation.com/u/ataya)\ **Post date:** [April 26, 2024, 12:51am UTC](https://forum.inductiveautomation.com/t/where-is-the-ignition-conf-file-in-a-docker-container/50303/8 "2024-04-26T00:51:22Z")
I have seen interesting behavior on this topic recently: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/2/223be4ae599be5fd0b78d7be902acf77d823ad5e.png) Should this trendline ever go above the redline? The max memory was set with `-m 10000` which is ~2gb below the pod resource request of `12000`. The JVM restarted 42 times, about every 10 minutes, so we took some corrective actions: 1. Increased pod limits to be more than the requests, from 12000 memory to 16000 memory, and 2 CPU to 8 CPU. 2. Updated ignition.conf to have init-memory and max-memory limits to be at 10000 to match `-m 10000` configuration. As a background, I have restored a `.gwbk` for initial configuration from another gateway, which had a setting of `56000` max memory in the file. Since the change where `ignition.conf` setting matched `-m`, it only went above the redline once, (I think thanks to max pod limit increase to 16000 the wrapper didn't send a SIGKILL (9)?) and has been stable since then. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/2/d2b6ae32a2e788a63d2a50341e47e3fa31e55f38.png) --- _[View the full topic](https://forum.inductiveautomation.com/t/where-is-the-ignition-conf-file-in-a-docker-container/50303)._