Long-Term Supported Versions

Environment Variable Persisting

Environment Variable Persisting

Function Description

In a system container, you can make the env variable persistent to the configuration file in the rootfs directory of the container by specifying the --env-target-file interface parameter.

Parameter Description

Command	Parameter	Value Description
isula create/run	--env-target-file	Variable of the string type. The env persistent file must be in the rootfs directory and must be an absolute path.

Constraints

If the target file specified by --env-target-file exists, the size cannot exceed 10 MB.
The parameter specified by --env-target-file must be an absolute path in the rootfs directory.
If the value of --env conflicts with that of env in the target file, the value of --env prevails.

Example

Start a system container and specify the env environment variable and --env-target-file parameter.

[root@localhost ~]# isula run -tid -e abc=123 --env-target-file /etc/environment --system-container --external-rootfs /root/myrootfs none init
b75df997a64da74518deb9a01d345e8df13eca6bcc36d6fe40c3e90ea1ee088e
[root@localhost ~]# isula exec b7 cat /etc/environment
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
TERM=xterm
abc=123

The preceding information indicates that the env variable (abc=123) of the container has been made persistent to the /etc/environment configuration file.

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.