add openeuler base image for amd64, arm64v8

[openeulerHW]

add openeuler base image for amd64, arm64v8
The root filesystem tar package is larger than 100M, we had to use git-lfs to upload it to github, completely pull of dist-amd64 and dist-arm64 branch also need git-lfs.

[github-actions]

Diff for 0dc6ceb:

failed fetching repo "openeuler"
unable to find a manifest named "openeuler" (in "/tmp/tmp.JoCYj7VLc1/oi/library" or as a remote URL)
tar: This does not look like a tar archive

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

[tianon]

Replying to #7982 here (since the PR with the issue is the appropriate place to have a discussion about it 😄):

I'm not sure if it is suitable to ask the question through filing a issue here, the guideline doesn't seem to metion the point.
As the pull request #7980 shows, our image have a rootfs package larger than 100M. Since github does not allow push such a big file directly, we use git-lfs to push it and thus causing the file cannot be pulled completely using git (it need to be pulled also using git-lfs). It seem to be the reason why this pull request failed the automatic check.
So is it means any official image should not including a package larger than 100M?

As you've discovered, we unfortunately don't yet support Git LFS (docker-library/bashbrew#10).

I'm very curious why the rootfs is over 100MB though -- isn't EulerOS an RPM-based distribution? What's included in that tarball which makes it so large? Surely there's room for improvement on the size (packages that don't make sense / aren't necessary in containers, kernel-related files, etc)?

[openeulerHW]

Replying to #7982 here (since the PR with the issue is the appropriate place to have a discussion about it 😄):

I'm not sure if it is suitable to ask the question through filing a issue here, the guideline doesn't seem to metion the point.
As the pull request #7980 shows, our image have a rootfs package larger than 100M. Since github does not allow push such a big file directly, we use git-lfs to push it and thus causing the file cannot be pulled completely using git (it need to be pulled also using git-lfs). It seem to be the reason why this pull request failed the automatic check.
So is it means any official image should not including a package larger than 100M?

As you've discovered, we unfortunately don't yet support Git LFS (docker-library/bashbrew#10).

I'm very curious why the rootfs is over 100MB though -- isn't EulerOS an RPM-based distribution? What's included in that tarball which makes it so large? Surely there's room for improvement on the size (packages that don't make sense / aren't necessary in containers, kernel-related files, etc)?

Got it, We will try to reduce the size of base image at next release.

[tianon]

On the next PR, you should also spend some time explaining what makes openEuler different from EulerOS (perhaps what they have in common as well), or link to some relevant documentation about the project that might help explain what makes it unique.

As additional context, the EulerOS image is already not being well-maintained (#5644 (comment)), and I'd hate to see a repeat of that.

[martin-g]

openEuler is an open-source Linux distribution with contributors from many organizations. It is governed by OpenAtom Foundation - similar to Linux Foundation but for Chinese OSS.
Some people say that it is based on RHEL but this is not really true. It just uses the RPM package management (DNF/YUM).
I am not sure how much technical details about openEuler I should share here, so I will just add a link to the latest technical white paper.

EulerOS is a commercial distro by Huawei. It is based on openEuler but adds proprietary software that optimizes it for Huawei's ARM64 hardware (Kunpeng and Ascend)

Disclaimer: I work for Huawei in the past few years!

I am pretty excited to work on and maintain the official Docker image for openEuler!
Unless something bad happens to me I plan to be around in the next several years!