Hey folks! I'm trying to rebuild the Bodhi image in staging Openshift, and I get this error:
# oc -n bodhi logs -f bc/bodhi-base Step 1/9 : FROM fedora:35 ---> b97d90f26110 Step 2/9 : LABEL name "bodhi-base" vendor "Fedora Infrastructure" license "MIT" ---> Running in 256c29c482ac ---> 0c9b2adcb2e8 Removing intermediate container 256c29c482ac Step 3/9 : RUN curl -v -o /etc/yum.repos.d/infra-tags-stg.repo https://infrastructure.fedoraproject.org/infra/ansible/files/common/fedora-infra-tags-stg.repo ---> Running in 073d7a95a91a * getaddrinfo() thread failed to start * Could not resolve host: infrastructure.fedoraproject.org * Closing connection 0 curl: (6) getaddrinfo() thread failed to start
It looks like the builder doesn't have network access. This used to work, the curl call has been there for quite some time.
I saw this error several times on F35 container, try to use F34 for now, it should help.
It seems like this is the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1990469
Metadata Update from @zlopez: - Issue priority set to: Waiting on Reporter (was: Needs Review)
Oh, unfortunately I do need to use F35. I'll follow the bug, thanks!
Metadata Update from @abompard: - Issue priority set to: Needs Review (was: Waiting on Reporter)
(or maybe try F36 ;-) )
Nope, same error for F36.
This is a known bug in Openshift 3.11 and it's not going to be fixed anytime soon. You'll need to migrate to OCP 4 cluster if you want to use F35+ images.
Yeah, this is due to the glibc in f35+ using new syscalls that old docker can't understand... ;(
There's no way to fix the 3.x cluster. We need to move to the 4.x ocp cluster. ;)
Luckily that shouldn't be too hard...
Metadata Update from @kevin: - Issue close_status updated to: Will Not/Can Not fix - Issue status updated to: Closed (was: Open)
It was simple indeed, thanks Kevin.
Metadata Update from @abompard: - Issue close_status updated to: None (was: Will Not/Can Not fix)
Login to comment on this ticket.