Description of problem: The Fedora 31 armhfp container image contains RAWHIDE content and therefore is unusable. Current behavior: # uname -m armv7l # sudo podman run --net=host --rm -ti registry.fedoraproject.org/fedora:31 cat /etc/fedora-release Fedora release 31 (Rawhide) Expected behavior is as this example from a X86_64 machine: $ uname -m x86_64 $ sudo podman run --net=host --rm -ti registry.fedoraproject.org/fedora:31 cat /etc/fedora-release Fedora release 31 (Thirty One) Also the problem does *not* existing with the Fedora 30 armhfp image.
This is related to the Fedora container image, not the "containers" package...
(In reply to Neal Gompa from comment #1) > This is related to the Fedora container image, not the "containers" > package... I apologize for the mistake. It probably would make life easier to add language names to components with ambiguous names - similar to the practice with python3-*
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
(In reply to Ben Cotton from comment #3) > This bug appears to have been reported against 'rawhide' during the Fedora > 32 development cycle. > Changing version to 32. No. Please read the bugs. This is an issue with the published Fedora 31 arm7l oci (docker) image, which is a rawhide image instead of a 31 GA image and thus unusable. It was not reported against 31 because at the time, there was no version 31 available for this component.
Yup, there's an issue with the creation, I've not had time to fix it.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.