RE: [opensuse-buildservice] no network in chroot
Hi, When obs building in chroot, there's missing '/etc/resolv.conf' file and causes no network within chroot. Is there any way to configure chroot's '/etc/resolv.conf' file in SPEC file, or project config file? Or is there any way the chroot could grab /etc/resolv.conf file from the host's /etc/resolv.conf file? Thanks, Rick -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wednesday 2013-05-29 17:36, Rick Liu wrote:
Hi,
When obs building in chroot, there's missing '/etc/resolv.conf' file and causes no network within chroot.
There is in general no network anyway during real building, so there is no point in providing resolv.conf. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wed, 2013-05-29 at 15:36 +0000, Rick Liu wrote:
Hi,
When obs building in chroot, there's missing '/etc/resolv.conf' file and causes no network within chroot.
Before I chroot, I copy the system's resolv.conf to the chroot /etc. I do not know that this makes sense in the OBS environment. But it does in my other uses. I also mount a few useful file systems so they appear correct. I have this is a script so it gets done 'automatically'. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Montag, 3. Juni 2013, 13:40:30 wrote Roger Oberholtzer:
On Wed, 2013-05-29 at 15:36 +0000, Rick Liu wrote:
Hi,
When obs building in chroot, there's missing '/etc/resolv.conf' file and causes no network within chroot.
Before I chroot, I copy the system's resolv.conf to the chroot /etc. I do not know that this makes sense in the OBS environment. But it does in my other uses. I also mount a few useful file systems so they appear correct. I have this is a script so it gets done 'automatically'.
In VM builds you do not even have network devices, so no, it does not make sense here. The goal is to have a 100% reproducable build with OBS. And an external network can always change. (Also we like to protect us and the internet from evil attacks). -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Adrian Schröter -
Jan Engelhardt -
Rick Liu -
Roger Oberholtzer