Long-Term Supported Versions

    Installing the OS

    Release Files

    The openEuler release files include ISO release packages, VM images, container images, and repo sources. The following tables describe those files respectively.

    Table 1 ISO release packages

    NameDescription
    openEuler-20.09-aarch64-dvd.isoBasic installation ISO file of the AArch64 architecture, including the core components for running the minimum system.
    openEuler-20.09-everything-aarch64-dvd.isoFull installation ISO file of the AArch64 architecture, including all components for running the entire system.
    openEuler-20.09-debuginfo-aarch64-dvd.isoISO file for openEuler debugging in the AArch64 architecture, including the symbol table information required for debugging.
    openEuler-20.09-x86_64-dvd.isoBasic installation ISO file of the x86_64 architecture, including the core components for running the minimum system.
    openEuler-20.09-everything-x86_64-dvd.isoFull installation ISO file of the x86_64 architecture, including all components for running the entire system.
    openEuler-20.09-debuginfo-x86_64-dvd.isoISO file for openEuler debugging in the x86_64 architecture, including the symbol table information required for debugging.
    openEuler-20.09-source-dvd.isoISO file of the openEuler source code.

    Table 2 VM images

    NameDescription
    openEuler-20.09.aarch64.qcow2.xzVM image of openEuler in the AArch64 architecture.
    openEuler-20.09.x86_64.qcow2.xzVM image of openEuler in the x86_64 architecture.

    NOTE:

    The default password of root user of the VM image is openEuler12#$. Change the password upon the first login.

    Table 3 Container images

    NameDescription
    openEuler-docker.aarch64.tar.xzContainer image of openEuler in the AArch64 architecture.
    openEuler-docker.x86_64.tar.xzContainer image of openEuler in the x86_64 architecture.

    Table 4 Repo sources

    NameDescription
    ISOStores ISO images.
    OSStores basic software package sources.
    debuginfoStores debugging package sources.
    docker_imgStores container images.
    virtual_machine_imgStores VM images.
    everythingStores full software package sources.
    extrasStores extended software package sources.
    sourceStores source code software package.
    updateStores upgrade software package sources.
    EPOLStores extended openEuler packages.

    Minimum Hardware Specifications

    The following table lists the minimum hardware specifications for openEuler 20.09.

    Table 5 Minimum hardware requirements

    ComponentMinimum Hardware Specification
    CPUKunpeng 920 (AArch64) / x86_64 (later than Skylake)
    Memory≥ 8 GB
    Hard drive≥ 120 GB

    Hardware Compatibility

    The following table lists the supported servers and configurations of openEuler.

    Table 6 Supported servers and configurations

    VendorServerServer ModelComponentTypical Configuration
    HuaweiTaiShan 2002280 balanced modelCPUKunpeng 920
    Memory4 x 32 GB 2933MHz
    NetworkTM210
    HuaweiFusionServer Pro2288H V5 rack serverCPUIntel(R) Xeon(R) Gold 5118 CPU @ 2.30GHz
    Memory4 x 32 GB 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.
    Bug Catching
    编组 3备份