On Mon, Apr 10, 2023, at 17:52, Reinhard Tartler wrote: > Control: tag -1 + unreproducible moreinfo > > Hi Kevin, > > great to hear from you in this space! > > On Thu, Feb 9, 2023 at 8:36 AM Kevin P. Fleming <ke...@km6g.us> wrote: >> Package: podman >> Version: 4.3.1+ds1-5+b1 >> Severity: important >> >> Dear Maintainer, >> >> I am seeing DNS resolution fail when using 'podman build' but succeed when >> using 'podman run', with a Dockerfile which contains the same commands I run >> manually in the 'podman run'-launched shell. >> >> Dockerfile >> ---------- >> FROM alpine:3.10 >> RUN cat /etc/resolv.conf >> RUN apk add tar > > Unfortunately, I can't reproduce. Please help me to reproduce this issue. > Also, maybe upstream has an idea, can you please report this issue at > https://github.com/containers/podman/issues/new/choose. In any case, here is > the output that I get: > > siretart@x1:/tmp/dnstest$ cat >> Containerfile > FROM alpine:3.10 > RUN cat /etc/resolv.conf > RUN apk add tar > siretart@x1:/tmp/dnstest$ cat Containerfile > FROM alpine:3.10 > RUN cat /etc/resolv.conf > RUN apk add tar > siretart@x1:/tmp/dnstest$ podman build . > STEP 1/3: FROM alpine:3.10 > Resolved "alpine" as an alias > (/etc/containers/registries.conf.d/shortnames.conf) > Trying to pull docker.io/library/alpine:3.10... > Getting image source signatures > Copying blob 396c31837116 done > Copying config e7b300aee9 done > Writing manifest to image destination > Storing signatures > STEP 2/3: RUN cat /etc/resolv.conf > search int.tauware.de > nameserver 10.0.2.3 > nameserver 192.168.88.3 > --> 2ce59772eaf > STEP 3/3: RUN apk add tar > fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/main/x86_64/APKINDEX.tar.gz > fetch > http://dl-cdn.alpinelinux.org/alpine/v3.10/community/x86_64/APKINDEX.tar.gz > (1/1) Installing tar (1.32-r1) > Executing busybox-1.30.1-r5.trigger > OK: 6 MiB in 15 packages > COMMIT > --> 7c1bfd9e030 > 7c1bfd9e030f07b05cc9427a97c0bc5ff73bca5436bce389ad81da1a64f64a11
Confirmed; I can no longer reproduce the problem. Something somewhere in the stack got fixed :-)