Installing the OS

Release Files

The following table lists the openEuler release files, including the ISO release packages, container images, VM images, and repo sources used online.

Table 1 openEuler release files

DirectoryTypeDescription
ISOISO release packagesThe directory differentiates the ISO release packages for the AArch64, x86, and source, respectively. The details are as follows:
  • openEuler-20.09-aarch64-dvd.iso and openEuler-20.09-x86_64-dvd.iso are the openEuler basic installation software package ISO files for the AArch64 and x86 architectures, respectively. The ISO files contain basic components running on the openEuler OS and meet the basic requirements of developers.
  • openEuler-20.09-everything-aarch64-dvd.iso and openEuler-20.09-everything-x86_64-dvd.iso are the openEuler full software package ISO files for the AArch64 and x86 architectures, respectively. In addition to all software in the openEuler basic installation software package, the ISO files also contain the software packages that have been verified in the openEuler community, which meet the advanced requirements of developers.
  • openEuler-20.09-debuginfo-aarch64-dvd.iso and openEuler-20.09-debuginfo-x86_64-dvd.iso are the openEuler debugging software package ISO files for the AArch64 and x86 architectures, respectively. The ISO files contain the symbol table information required for debugging and are used for debugging software functions and performance.
  • openEuler-20.09-source-dvd.iso is the ISO file that contains all source code software packages of the openEuler community, which is used offline by developers.
Note:

Each ISO release package has its own verification file, which is used to verify the integrity of the ISO release package.

docker_imgContainer imagesThe openEuler container image, which provides only the basic bash environment, is used as the basic container image. The directory differentiates the container images for the AArch64 and x86 architectures, respectively.
Note:

Each container image has its own verification file, which is used to verify the integrity of the container image.

virtual_machine_imgVM images

The openEuler VM image provides only the basic running environment to shorten the VM deployment time. The directory differentiates the VM images for the AArch64 and x86 architectures, respectively.

Note:
  • The default password of the root user of the VM image is openEuler12#$. Change the password upon the first login.
  • Each VM image has its own verification file, which is used to verify the integrity of the VM image.
EPOLRepo sourcesThe repo sources of the openEuler third-party software package are mainly contributed by third parties and communities, and are maintained by the providers. The directory differentiates the repo sources for the AArch64 and x86 architectures, respectively.
OSThe repo source of the openEuler basic installation software package provides the offline version upgrade function. The content of the software package is the same as that of the basic installation software package ISO in the ISO release package. The directory differentiates the repo sources for the AArch64 and x86 architectures, respectively.
debuginfoThe repo source of the openEuler debugging software package provides the online download function. The content of the software package is the same as that of the debugging software package ISO in the ISO release package. The directory differentiates the repo sources for the AArch64 and x86 architectures, respectively.
everythingThe repo source of the openEuler full software package provides the online download and version upgrade functions. The content of the software package is the same as that of the full software package ISO in the ISO release package. The directory differentiates the repo sources for the AArch64 and x86 architectures, respectively.
sourceThe repo source of all source code software packages in the openEuler community, which is used online by developers.
updateThe repo source of the openEuler upgrade software package, which is used to fix bugs and common vulnerabilities and exposures (CVE) in released versions and to update and release software with enhancements. It provides online download and software upgrade functions. The directory differentiates the repo sources for the AArch64 and x86 architectures, respectively.

Minimal Hardware Specifications

Table 2 lists the minimum hardware specifications for installing openEuler 20.09.

Table 2 Minimal hardware specifications

ComponentMinimal Hardware Specification
CPUKunpeng 920 (architecture: AArch64)
x86-64 (Skylake or later)
Memory≥ 8 GB
Hard disk≥ 120 GB

Hardware Compatibility

Table 3 lists the typical configurations of servers and components supported by openEuler. openEuler will gradually support other servers in the future. Partners and developers are welcome to participate in the contribution and validation.

Table 3 Supported servers and typical configurations

VendorServerServer ModelComponentTypical Configuration
HuaweiTaiShan 2002280 balanced modelCPUKunpeng 920
Memory32G*4 2933MHz
NetworkTM210
HuaweiFusionServer Pro2288H V5 rack serverCPUIntel(R) Xeon(R) Gold 5118 CPU @ 2.30GHz
Memory32*4 2400MHz
NetworkX722

Bug Catching

Buggy Content

Bug Description

Submit As Issue

It's a little complicated....

I'd like to ask someone.

PR

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.

How satisfied are you with this document

Not satisfied at all
Very satisfied
Submit
Click to create an issue. An issue template will be automatically generated based on your feedback.