Long-Term Supported Versions


    Command Line Interface List

    This section lists commands in system containers, which are different from those in common containers. For details about other commands, refer to sections related to the iSulad container engine or run the isula XXX --help command.



    Value Description

    isula create/run


    • Variable of the string type.
    • Absolute path on the host.
    • Specifies the rootfs of a VM when running a system container.


    • Boolean variable.
    • Specifies whether a container is a system container. In a system container scenario, this function must be enabled.


    • Variable of the string type.
    • Specifies the hosts configuration for a container. The format is hostname:ip. Multiple values can be set.

    --dns, --dns-option, --dns-search

    • Variable of the string type.
    • Specifies the DNS configuration for a container. Multiple values can be set.


    • Variable of the string type.
    • Container namespace kernel parameter. The value can only be net or ipc. If multiple values are set, separate them with commas (,), for example, --ns-change-opt=net,ipc.


    • Boolean variable.
    • Indicates whether to enable the oom-kill-disable function.


    • Variable of the string type.
    • Sets the size of /dev/shm. The default value is 64 MB. The unit can be byte (B), kilobyte (KB), megabyte (MB), gigabyte (GB), terabyte (TB), or petabyte (PB).


    • Variable of the string type.
    • Specifies container kernel parameters. The format is key=value. Multiple values can be set. The sysctl whitelist is as follows:

    kernel.msgmax, kernel.msgmnb, kernel.msgmni, kernel.sem, kernel.shmall, kernel.shmmax, kernel.shmmni, kernel.shm_rmid_forced, kernel.pid_max, net., and fs.mqueue


    The kernel.pid_max kernel parameter in a container must be able to be namespaced. Otherwise, an error is reported.

    Parameter restrictions (including the parameter types and value ranges) of the sysctl whitelist in a container must be the same as those of kernel parameters in the physical machine.


    • Variable of the string type.
    • Specifies the env persistent file path. (The path must be an absolute path and the file must be in the rootfs directory.) The file size cannot exceed 10 MB. If the value of --env conflicts with that of env in the file, the value of --env takes effect.
    • The root directory of the absolute path is the rootfs root directory. That is, to set the file path to /etc/environment in the container, you need to specify env-target-file=/etc/environment only.


    • Variable of the string type.
    • Specifies the cgroup parent directory of a container. The cgroup root directory is /sys/fs/cgroup/controller.


    • Variable of the string type.
    • Specifies the memory space shared between the host and a container (tmpfs). The format is as follows:

    host path:container path:rw/ro:size limit


    • Variable of the string type.
    • Specifies the maximum number of file handles in a container. The value must be an integer.


    • Variable of the string type.
    • The parameter format is uid:gid:offset.

    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备份