# Add ulimit flag to Flow docker container

**URL:** <https://forum.flow.com/t/add-ulimit-flag-to-flow-docker-container/4362>\
**Category:** Node Operations\
**Created:** [February 22, 2023, 11:56am UTC](https://forum.flow.com/t/add-ulimit-flag-to-flow-docker-container/4362 "2023-02-22T11:56:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vishal](https://avatars.discourse-cdn.com/v4/letter/v/49beb7/32.png) [@vishal](https://forum.flow.com/u/vishal)\
**Post date:** [February 22, 2023, 11:56am UTC](https://forum.flow.com/t/add-ulimit-flag-to-flow-docker-container/4362/1 "2023-02-22T11:56:25Z")

</div>

For the upcoming flow mainnet spork on 22nd Feb (see [announcement](http://forum.flow.com/t/emergency-mainnet-spork-on-2023-02-22/4325)), please also add this additional `ulimit` parameter to the docker configuration for all node types.

`--ulimit nofile=8192`

Example of the docker config with the flag is [here](https://developers.flow.com/nodes/node-operation/node-setup#access).

This higher ulimit is required to address the networking issue that was observed earlier, where some nodes failed to connect to other nodes. More on the issue [here](https://developers.flow.com/nodes/node-operation/faq#why-do-i-need-to-update-my-nodes-ulimit).

Thank you,  
Flow Team.