multiarch / centos Goto Github PK

This ticket is to share the info about coming CentOS 8 architecture info.

CentOS 8 build status

CentOS 8.0.1905 build status
https://www.centos.org/forums/viewtopic.php?f=10&t=70501

Architectures

https://wiki.centos.org/About/Building_8#head-c2699098ec0696d4d4aafbd404d74fa37546a8ec

• Main architectures: x86_64, ppc64le (Little Endian), aarch64 (ARM64 , ARMv8)
• AltArch: armhfp (ARM32, ARMv7 - aka armv7hl)

I get the error message in the title when I try to run:

yum update.

I'm running a fedora 24 as the host, I run:
docker run --rm --privileged multiarch/qemu-user-static:register

before starting the centos container.
I'm using the fedora docker package not the docker.io package.
Here is the printout of docker info :

[rspazzol@localhost origin]$ docker info
Containers: 2
Running: 0
Paused: 0
Stopped: 2
Images: 21
Server Version: 1.10.3
Storage Driver: devicemapper
Pool Name: docker-253:1-2230976-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 5.335 GB
Data Space Total: 107.4 GB
Data Space Available: 34.55 GB
Metadata Space Used: 5.39 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.142 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev or use --storage-opt dm.no_warn_on_loop_devices=true to suppress this warning.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.122 (2016-04-09)
Execution Driver: native-0.2
Logging Driver: journald
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 4.6.7-300.fc24.x86_64
Operating System: Fedora 24 (Workstation Edition)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 0
CPUs: 4
Total Memory: 19.04 GiB
Name: localhost.localdomain
ID: ZITI:QGE4:AX63:Y4HG:QY72:AGBZ:6UGQ:44ZQ:3V7F:FW3P:7LB4:AAGA
Registries: docker.io (secure)

Right now multiarch CentOS container image is only armhfp (and x86_64).
And even the container image have an issue (#1).
I feel that I will want to try an experiment by a different approach.

That is to get an archive tar file not from *.iso or other archive files on CentOS project, but also to get it from DockerHub or CentOS's official container repository URL.

Here is the example for Red Hat Enterprise Linux (RHEL).
In this case, I am using skopeo command to achieve the approach.
https://github.com/junaruga/multiarch-rhel-experiment

This related to multiarch/qemu-user-static#66 .

seeing

https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#add-or-copy
Although ADD and COPY are functionally similar, generally speaking, COPY is preferred.
...
For other items (files, directories) that do not require ADD’s tar auto-extraction capability, you should always use COPY.

Maybe this code is the case to change from ADD to COPY.
https://github.com/multiarch/centos/blob/master/update.sh#L103

ADD qemu-${qemu_arch}-static /usr/bin

Hello,

Currently, the latest version available in multiarch is 7.2.
It would be very appreciated if you could build version 7.3 (released some months ago) too.

NB: I've tried a little to prepare some patchs for a PR, but I've had difficulties to run successfully update.sh, and couldn't make it myself.

During the building, could you check that aarch64 has its variant -clean in dockerhub (as there is x86_64 and armhf).
This is the variant that we used for scaleway/image-centos, and it's currently missing (no tag 7.2.1511-aarch64-clean).

Thanks a lot for help !