yum install is broken in buildah images
paleozogt opened this issue · 1 comments
paleozogt commented
Description
We use the quay.io buildah images in our cicd pipelines, and recently yum install stopped working.
Steps to reproduce the issue:
docker run --rm -it quay.io/buildah/stable:v1.26.0 yum install -y python3-pip
Describe the results you received:
yum fails do to bad repo mirrors.
Describe the results you expected:
To successfully be able to yum install things.
Output of rpm -q buildah
or apt list buildah
:
$ docker run --rm -it quay.io/buildah/stable:v1.26.0 yum install -y python3-pip
Fedora 36 - x86_64 16 MB/s | 81 MB 00:05
Fedora 36 openh264 (From Cisco) - x86_64 2.3 kB/s | 2.5 kB 00:01
Fedora Modular 36 - x86_64 0.0 B/s | 0 B 00:01
Errors during downloading metadata for repository 'fedora-modular':
- Curl error (56): Failure when receiving data from the peer for http://ftp.tudelft.nl/download.fedora.redhat.com/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml [Recv failure: Connection reset by peer]
- Status code: 404 for https://d2lzkl7pfhq30w.cloudfront.net/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml (IP: 65.8.234.185)
- Status code: 404 for https://dl.fedoraproject.org/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml (IP: 38.145.60.24)
- Curl error (56): Failure when receiving data from the peer for http://dl.fedoraproject.org/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml [Recv failure: Connection reset by peer]
- Curl error (56): Failure when receiving data from the peer for http://mirror.rnet.missouri.edu/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml [Recv failure: Connection reset by peer]
Error: Failed to download metadata for repo 'fedora-modular': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Output of buildah version
:
Version: 1.26.0
Go Version: go1.18
Image Spec: 1.0.2-dev
Runtime Spec: 1.0.2-dev
CNI Spec: 1.0.0
libcni Version: v1.1.0
image Version: 5.21.1
Git Commit:
Built: Wed May 4 19:49:14 2022
OS/Arch: linux/amd64
BuildPlatform: linux/amd64
Output of cat /etc/*release
:
Fedora release 36 (Thirty Six)
NAME="Fedora Linux"
VERSION="36 (Container Image)"
ID=fedora
VERSION_ID=36
VERSION_CODENAME=""
PLATFORM_ID="platform:f36"
PRETTY_NAME="Fedora Linux 36 (Container Image)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:36"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f36/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=36
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=36
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Container Image"
VARIANT_ID=container
Fedora release 36 (Thirty Six)
Fedora release 36 (Thirty Six)
cpe:/o:fedoraproject:fedora:36
Output of uname -a
:
Linux 5a92382855ac 6.2.0-1014-aws #14~22.04.1-Ubuntu SMP Thu Oct 5 22:43:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
flouthoc commented
@paleozogt This looks like network flake to me, it is reproduceable ?