Bug 1201989 - Building a container image with "podman" leaves empty /etc/resolv.conf behind
Summary: Building a container image with "podman" leaves empty /etc/resolv.conf behind
Status: NEW
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Michael Schröder
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-29 17:05 UTC by Klaus Kämpf
Modified: 2022-08-03 05:52 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Klaus Kämpf 2022-07-29 17:05:11 UTC 
Due to https://bugzilla.suse.com/show_bug.cgi?id=1201894, I switched isv:Rancher:Elemental to use "podman" instead of "docker" as the BuildEngine.

While the images built fine, DNS resolution within the booted image failed.

Turns out that "podman" leaves an empty "/etc/resolv.conf" behind which won't be touched by the network stack.

Removing /etc/resolv.conf and restarting the network restored DNS resolution.


As bsc#1201894 is fixed meanwhile, I switch this project back to building with docker.

Still I consider this a bug within the "build with podman" setup in OBS.
Comment 1 Richard Brown 2022-08-02 08:17:14 UTC 
I am not responsible for how OBS uses podman, and I'm not able to recreate this problem with regular podman in Tumbleweed