# Unable to change env variable MAX\_COMMIT\_ITERATIONS in Docker Container

**URL:** https://forum.genieacs.com/t/unable-to-change-env-variable-max-commit-iterations-in-docker-container/6045
**Category:** Uncategorized
**Created:** [October 17, 2024, 2:47pm UTC](https://forum.genieacs.com/t/unable-to-change-env-variable-max-commit-iterations-in-docker-container/6045 "2024-10-17T14:47:20Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jpis](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jpis](https://forum.genieacs.com/u/jpis)
#### Post date: [October 17, 2024, 2:47pm UTC](https://forum.genieacs.com/t/unable-to-change-env-variable-max-commit-iterations-in-docker-container/6045/1 "2024-10-17T14:47:20Z")

</div>

We are currently running GenieACS from a docker container Image. I Followed this instalation tutorial:

> **[GitHub - GeiserX/genieacs-docker: Automated configuration files for your GenieACS...](https://github.com/GeiserX/genieacs-docker)**
>
> Automated configuration files for your GenieACS deployment

My current version is: v1.2.13+2407184eca

I used docker-compose for setting up the application. Here are my enviroment variables:

```auto
- GENIEACS_UI_JWT_SECRET= ---

- GENIEACS_CWMP_ACCESS_LOG_FILE=/var/log/genieacs/genieacs-cwmp-access.log

- GENIEACS_NBI_ACCESS_LOG_FILE=/var/log/genieacs/genieacs-nbi-access.log

- GENIEACS_FS_ACCESS_LOG_FILE=/var/log/genieacs/genieacs-fs-access.log

- GENIEACS_UI_ACCESS_LOG_FILE=/var/log/genieacs/genieacs-ui-access.log

- GENIEACS_DEBUG_FILE=/var/log/genieacs/genieacs-debug.yaml
            
- GENIEACS_EXT_DIR=/opt/genieacs/ext

- GENIEACS_MONGODB_CONNECTION_URL=mongodb://mongo/genieacs
            
- GENIEACS_MAX_COMMIT_ITERATIONS=512
            
- GENIEACS_EXT_TIMEOUT=30000

```

I ran into the fault “too many commits iterations” after running a heavy provision script. I tried changing several times the value of GENIEACS\_MAX\_COMMIT\_ITERATIONS but the provision returned the same error at the same part of the script. It appears this doesn’t make any change.

I ran the same script in a test server that has GenieACS installed directly with npm acording to installation process in docs. The script ran into the same error until I changed GENIEACS\_MAX\_COMMIT\_ITERATIONS=64 in genieacs.env.

In my docker image, i kept falling into commits fault even with GENIEACS\_MAX\_COMMIT\_ITERATIONS=512.

After changing the evn variables in docker-compose.yml I executed docker restart.

Can any one help me with this issue.

---

<div class="post-metadata">

### Author: ![akcoder](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/akcoder/32/11_2.png) [@akcoder](https://forum.genieacs.com/u/akcoder)
#### Post date: [October 17, 2024, 4:36pm UTC](https://forum.genieacs.com/t/unable-to-change-env-variable-max-commit-iterations-in-docker-container/6045/2 "2024-10-17T16:36:14Z")

</div>

You need to solve the actual issue. Changing the MAX\_COMMIT\_ITERATIONS to a value 16x the default is not going to work.

For the CPE in question, [enable debug logging](https://forum.genieacs.com/t/too-many-commit-iterations/238/9), then look through the values being sent to the CPE. You will find that one of the parameters is being set to a changing value.
