On 5/6/19 11:57 AM, Jun Aruga wrote:
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)
updating images in docker hub requires a human to file a pull request
with the exact image that needs to be pulled. It's not automated at all.
For a long time also, docker hub didn't do anything except x86_64.
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.
Kevin, I have a question.
https://pagure.io/pungi-fedora/blob/f30/f/fedora-final.conf#_322
> > 'arches': ['armhfp', 'aarch64', 'ppc64le',
's390x', 'x86_64'],
From above setting for Container, ideally those 5 archs should be
released on URL [a] or [b]?
Yes. :)
The primary arches will be at a, the alternative arches will be at b.
Where is ppc64le's image?
Thats an alternative arch, so it would be at b (fedora-secondary).
(If it composed with the final release)
Yes. This is a koji setting thats passed to 'oz' for the images. Before
Fedora 22 we used yum, after Fedora 22 dnf was used.
c is for when a release is in development (ie, before final release).
kevin