Long-Term Supported Versions

    Maximum Number of Handles

    Function Description

    System containers support limit on the number of file handles. File handles include common file handles and network sockets. When starting a container, you can specify the --files-limit parameter to limit the maximum number of handles opened in the container.

    Parameter Description



    Value Description

    isula create/run



    • The value cannot be negative and must be an integer.
    • The value 0 indicates that the number is not limited by the parameter. The maximum number is determined by the current kernel files cgroup.


    • If the value of --files-limit is too small, the system container may fail to run the exec command and the error "open temporary files" is reported. Therefore, you are advised to set the parameter to a large value.
    • File handles include common file handles and network sockets.


    To use --files-limit to limit the number of file handles opened in a container, run the following command to check whether the kernel supports files cgroup:

    [root@localhost ~]# cat /proc/1/cgroup | grep files

    If files is displayed, files cgroup is supported.

    Start the container, specify the --files-limit parameter, and check whether the files.limit parameter is successfully written.

    [root@localhost ~]# isula run  -tid --files-limit 1024 --system-container  --external-rootfs /tmp/root-fs  empty init 01e82fcf97d4937aa1d96eb8067f9f23e4707b92de152328c3fc0ecb5f64e91d 
    [root@localhost ~]# isula exec -it 01e82fcf97d4 bash 
    [root@localhost ~]# cat /sys/fs/cgroup/files/files.limit 

    The preceding information indicates that the number of file handles is successfully limited in the container.

    Bug Catching

    Buggy Content

    Bug Description

    Submit As Issue

    It's a little complicated....

    I'd like to ask someone.


    Just a small problem.

    I can fix it online!

    Bug Type
    Specifications and Common Mistakes

    ● Misspellings or punctuation mistakes;

    ● Incorrect links, empty cells, or wrong formats;

    ● Chinese characters in English context;

    ● Minor inconsistencies between the UI and descriptions;

    ● Low writing fluency that does not affect understanding;

    ● Incorrect version numbers, including software package names and version numbers on the UI.


    ● Incorrect or missing key steps;

    ● Missing prerequisites or precautions;

    ● Ambiguous figures, tables, or texts;

    ● Unclear logic, such as missing classifications, items, and steps.


    ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

    ● Incorrect schematic or architecture diagrams;

    ● Incorrect commands or command parameters;

    ● Incorrect code;

    ● Commands inconsistent with the functions;

    ● Wrong screenshots.

    Risk Warnings

    ● Lack of risk warnings for operations that may damage the system or important data.

    Content Compliance

    ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

    ● Copyright infringement.

    How satisfied are you with this document

    Not satisfied at all
    Very satisfied
    Click to create an issue. An issue template will be automatically generated based on your feedback.
    Bug Catching
    编组 3备份