Bug 2123246
Summary: | cri-o: run `podman build` failed with "Curl error (6): Couldn't resolve host name" | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | HuijingHei <hhei> |
Component: | conmon | Assignee: | Peter Hunt <pehunt> |
Status: | CLOSED DUPLICATE | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | CentOS Stream | CC: | bstinson, jwboyer, nalin, pehunt, tsweeney, walters, ypu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-02-14 15:21:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
HuijingHei
2022-09-01 08:38:28 UTC
Not sure this is the right component, feel free to change if not correct Thanks Yiqiao for the help to find the root cause. Additional info, can not reproduce on 412.86.202208311537-0 $ rpm -q podman cri-o podman-4.2.0-1.rhaos4.12.el8.x86_64 cri-o-1.25.0-51.rhaos4.12.git315a0cb.el8.x86_64 This is the same as bug #2123251. (In reply to Nalin Dahyabhai from comment #3) > This is the same as bug #2123251. Not quite the same, as can not reproduce with 412.86.202208311537-0, I would say it is a regression issue we've recently added a `/etc/crio/seccomp.json` to openshift nodes for cri-o. I would say it's the same root cause: podman and buildah shouldn't be reading that file by default. Got it, thanks! If in this case, maybe can dup this to bug #2123251. Verify passed with podman-4.4.0-1.el9.x86_64, podman build read file "/usr/share/containers/seccomp.json" [core@cosa-devsh ~]$ rpm -q podman cri-o podman-4.4.0-1.el9.x86_64 cri-o-1.26.1-4.rhaos4.13.gita78722c.el9.x86_64 [core@cosa-devsh ~]$ sudo find /etc/ /usr/ -name "seccomp.json" /etc/crio/seccomp.json /usr/etc/crio/seccomp.json /usr/share/containers/seccomp.json [core@cosa-devsh ~]$ cat Dockerfile FROM registry.fedoraproject.org/fedora:36 RUN dnf -y install systemd dnsmasq iproute iputils && dnf clean all && systemctl enable dnsmasq [core@cosa-devsh ~]$ podman --log-level debug build --no-cache -t dnsmasq . DEBU[0003] Resources: &define.CommonBuildOptions{AddHost:[]string{}, OmitHistory:false, CgroupParent:"", CPUPeriod:0x0, CPUQuota:0, CPUShares:0x0, CPUSetCPUs:"", CPUSetMems:"", HTTPProxy:true, IdentityLabel:0x1, Memory:0, DNSSearch:[]string{}, DNSServers:[]string{}, DNSOptions:[]string{}, LabelOpts:[]string(nil), MemorySwap:0, NoHosts:false, NoNewPrivileges:false, OmitTimestamp:false, SeccompProfilePath:"/usr/share/containers/seccomp.json", ApparmorProfile:"", ShmSize:"65536k", Ulimit:[]string{}, Volumes:[]string{}, Secrets:[]string{}, SSHSources:[]string{}, OCIHooksDir:[]string{}} Hi Peter, can we close it as the issue is fixed? I am also OK to make it as duplicated, thanks! yeah it sounds like this is fixed, we can track it over there *** This bug has been marked as a duplicate of bug 2123251 *** |