Specifying Rootfs to Create a Container

Function Description

Different from a common container that needs to be started by specifying a container image, a system container is started by specifying a local root file system (rootfs) using the --external-rootfs parameter. The rootfs contains the operating system environment on which the container depends during running.

Parameter Description

Command	Parameter	Value Description
isula create/run	--external-rootfs	Variable of the string type. Absolute path in the root file system of the container, that is, the path of the rootfs.

Constraints

The rootfs directory specified using the --external-rootfs parameter must be an absolute path.
The rootfs directory specified using the --external-rootfs parameter must be a complete OS environment including systemd package. Otherwise, the container fails to be started.
When a container is deleted, the rootfs directory specified using --external-rootfs is not deleted.
Containers based on an ARM rootfs cannot run in the x86 environment. Containers based on an x86 rootfs cannot run in the ARM environment.
You are advised not to start multiple container instances in the same rootfs. That is, one rootfs is used by only one container instance that is in the lifecycle.

Example

Assuming the local rootfs path is /root/myrootfs, run the following command to start a system container:

# isula run  -tid --system-container --external-rootfs /root/myrootfs none init

NOTE:
The rootfs is a user-defined file system. Prepare it by yourself. For example, a rootfs is generated after the TAR package of a container image is decompressed.

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.

Usability

● Incorrect or missing key steps;

● Missing prerequisites or precautions;

● Ambiguous figures, tables, or texts;

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

Correctness

● 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.

We may contact you through email in regard to the bug fixing solution. You will also be notified through email if you win any prize during the activity.