> And why below s390x does not have
Fedora-Container-Base-*.tar.xz?
Those are things that failed in the final RC2 compose of Fedora30.
Since they were not release blocking, they... didn't block the release.
...snip...
>
> I change my question.
> Do you know who is creating this kind of multi arch container images?
>
https://dl.fedoraproject.org/pub/fedora/linux/releases/30/Container/aarch...
Those were all made by the Fedora 30 rc2 compose.
pungi is the tool, and this:
https://pagure.io/pungi-fedora/blob/f30/f/fedora-final.conf
was the config used.
Does that answer the question?
Yes, Kevin. Thank you for the info.
What I do not understand is below DockerHub has Feodra 30 ppc64le,
Fedora 29 armhfp that Fedora Project did not release.
https://hub.docker.com/r/ppc64le/fedora/
Fedora 29, 30
https://hub.docker.com/r/arm32v7/fedora/
Fedora 29 (not 30)
Anyway, as what I wanted is layer.tar in the image archive, maybe I
will take it from DockerHub's image like this.
$ docker pull arm32v7/fedora:29
$ docker save arm32v7/fedora:29 -o 29-armhfp.tar
$ tar -xf 29-armhfp.tar
$ ls -l */layer.tar
-rw-r--r-- 1 jaruga jaruga 256970240 Feb 20 14:00
88edf58c1d5b3ee606b724b19ac4b4866b20ba93d15d5b330fc6cc29055b480b/layer.tar
Thanks. Solved.
--
Jun Aruga / He - His - Him
jaruga(a)redhat.com / IRC: jaruga