Kevin and Clement, thanks for the explanation.
I am looking forward to seeing the final compose.
So, likely we haven't had a armv7 fedora 30 compose recently, and
so no
one has updated it. The container sig would be the ones to ask here.
Sure, I will subscribe the mailing list.
Yes I do the Dockerhub updates, and since we did not have a full
compose working in a while I did my best to at least get something out
for fedora 30.
Thank you for your work! I appreciate it.
The problem we have with the compose is tracked in this ticket -->
https://pagure.io/releng/issue/8173
Sure, I will subscribe it.
By the way, let me tell you why I want the mult arch Container.
I am working for multiarch project now [1].
As you may know, when we build or run different arch container (ex.
aarch64) on the host arch (ex. x86_64), we can not do it.
```
$ docker run --rm -t arm64v8/fedora:30 uname -m
standard_init_linux.go:207: exec user process caused "no such file or
directory"
```
But below commands should work on your x86_64 host OS.
As it is not officially released on the multiarch project, it is still
my private container repository.
$ docker run --rm --privileged multiarch/qemu-user-static:register --reset
$ docker run --rm -t quay.io/junaruga/multiarch-fedora:30-aarch64 uname -m
aarch64
$ docker run --rm -t quay.io/junaruga/multiarch-fedora:30-s390x uname -m
s390x
This technology enables you to debug your app on the multi arch
environment on local easily or add the environment to your x86_64 base
CI.
If you are interested in how it works, see [2] and [3].
[1] multiarch project:
https://github.com/multiarch
[2]
https://github.com/multiarch/qemu-user-static
[3]
https://github.com/multiarch/fedora
--
Jun Aruga / He - His - Him
jaruga(a)redhat.com / IRC: jaruga