Dne 30.5.2018 v 16:24 Todd Zullinger napsal(a):
> But testing this briefly, the host resolv.conf still ends up
> in the chroot. I'm probably overlooking something obvious.
> At least, I hope I am.
No, you do not overlook anything. I checked systemd code and they simply
generate resolv.conf
On 30.5.2018 16:48, Todd Zullinger wrote:
This works:
touch /etc/mock/empty
echo "config_opts['nspawn_args'] = ['--bind=/etc/mock/empty:/etc/resolv.conf']"
\
>> /etc/mock/site-defaults.cfg
sh-4.4# time curl http://example.com/
curl: (6) Could not resolve host: example.com
real
El mié, 30-05-2018 a las 14:33 +0200, Miro Hrončok escribió:
> On 30.5.2018 14:09, Miro Hrončok wrote:
> > So I decided to test this. I've added the following to the spec:
> >
> > time curl http://example.com/
> >
> > Here are the times:
> >
> > * my mock: real 0m56.595s Could not
I wrote:
> It should be possible to manually override the resolv.conf
> now by bind mounting an empty file on /etc/resolv.conf in
> the chroot. I've been meaning to play with this, but have
> not made time to do it until just now.
>
> I thought something like this would work:
>
> touch
Miro Hrončok wrote:
> Hi, since our Koji builds have disabled internet access, I want to do the
> same, so I have more Koji consistent builds.
>
> I have the following in /etc/mock/site-defaults.cfg:
>
> config_opts['use_host_resolv'] = True # or False, no difference
>
On 30.5.2018 14:09, Miro Hrončok wrote:
So I decided to test this. I've added the following to the spec:
time curl http://example.com/
Here are the times:
* my mock: real 0m56.595s Could not resolve host
* Koji: real 0m0.030s Could not resolve host
And copr: real 0m40.578s
Hi, since our Koji builds have disabled internet access, I want to do
the same, so I have more Koji consistent builds.
I have the following in /etc/mock/site-defaults.cfg:
config_opts['use_host_resolv'] = True # or False, no difference
config_opts['rpmbuild_networking'] = False
The
