# Edit RAM in Docker on NAS Synology **URL:** \ **Category:** Ignition\ **Tags:** docker\ **Created:** [February 16, 2024, 3:12pm UTC](https://forum.inductiveautomation.com/t/edit-ram-in-docker-on-nas-synology/85842 "2024-02-16T15:12:23Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Jerome\_Legrand](https://avatars.discourse-cdn.com/v4/letter/j/e8c25b/32.png) [@Jerome\_Legrand](https://forum.inductiveautomation.com/u/Jerome_Legrand)\ **Post date:** [February 16, 2024, 3:12pm UTC](https://forum.inductiveautomation.com/t/edit-ram-in-docker-on-nas-synology/85842/1 "2024-02-16T15:12:23Z")
Hi, Sorry in advance for my bad english. I search how to change the RAM maximum allocation in Maker from a docker in a Synology. I found I have to change the data in the ignition.conf file but I don't find how to edit it... I try to change it from Docker terminal but I can't be root on it... I try to link the folder to a folder of the synology but I corrupt the instance of the docker... Does any one have do this ? Thank you in advance. Regards. ---
**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:** [February 16, 2024, 3:23pm UTC](https://forum.inductiveautomation.com/t/edit-ram-in-docker-on-nas-synology/85842/2 "2024-02-16T15:23:20Z")
In _Container Manager_ within DSM, you can set command arguments here: ![SCR-20240215-pruj](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/1/d120e1ad499d5011793dd95ef1be674502792d5b.png) Specifically you're looking to add something like `-m 2048` to set a 2GB max heap memory setting. See the [Runtime Arguments](https://www.docs.inductiveautomation.com/docs/8.1/platform/docker-image#runtime-arguments) section of the Docker Image docs for more information. ---
**Author:** ![Jerome\_Legrand](https://avatars.discourse-cdn.com/v4/letter/j/e8c25b/32.png) [@Jerome\_Legrand](https://forum.inductiveautomation.com/u/Jerome_Legrand)\ **Post date:** [February 16, 2024, 3:38pm UTC](https://forum.inductiveautomation.com/t/edit-ram-in-docker-on-nas-synology/85842/3 "2024-02-16T15:38:35Z")
Thank you fot this answer. I have create a new instance with a correct RAM. For do this, the only solution is to create a new instance. No modification possible on an existing instance ? ---
**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:** [February 16, 2024, 4:10pm UTC](https://forum.inductiveautomation.com/t/edit-ram-in-docker-on-nas-synology/85842/4 "2024-02-16T16:10:51Z")
I suppose you could simply shell into the container and modify the `data/ignition.conf` file to set the memory value there. But ideally, you want to associate a persistent data volume with your container so that you can recreate as needed and not lose your gateway state. ---
**Author:** ![Jerome\_Legrand](https://avatars.discourse-cdn.com/v4/letter/j/e8c25b/32.png) [@Jerome\_Legrand](https://forum.inductiveautomation.com/u/Jerome_Legrand)\ **Post date:** [February 17, 2024, 4:13pm UTC](https://forum.inductiveautomation.com/t/edit-ram-in-docker-on-nas-synology/85842/5 "2024-02-17T16:13:24Z")
I try to edit the ignition.conf file by a container terminal but I not root... And I don't find a solution to be root on the terminal... I can't install a edition file in terminal... Thank for this solution, if I need to upgrade the RAM later, I will do a full backup and create a new instance. My database for historian isn't in the container so I normally lose nothing.... ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 17, 2024, 4:43pm UTC](https://forum.inductiveautomation.com/t/edit-ram-in-docker-on-nas-synology/85842/6 "2024-02-17T16:43:09Z")
If you've configured your container to load a gateway backup at startup, you can simply modify the `ignition.conf` file that is **in** the backup.