On Fri, Aug 19, 2022 at 04:50:07PM +0200, Florian Weimer wrote:
* Stephen Smoogen:
> On Fri, 19 Aug 2022 at 05:44, Florian Weimer <fweimer(a)redhat.com> wrote:
>
> * Kevin Fenzi:
>
> > Greetings everyone.
> >
> > Many years ago mock introduced and then made default it's isolation to
> > use systemd-nspawn instead of chroot. Shortly after the nspawn isolation
> > was added, it was used in fedoraproject koji builds, but there were
> > issues and since then the fedoraproject koji has defaulted to using
> > chroot isolation.
> >
> > Releng has had a ticket open for a long time to switch
> > (
https://pagure.io/releng/issue/6967 )
> >
> > I think the two items listed there (kernel bind mounts and loop devices)
> > have long since been fixed, so I would like to propose we switch rawhide
> > to using nspawn and see if any other issues show up.
>
> What's the version of nspawn that will be used here? Presumably it's
> not the rawhide version, but the host version?
>
> Currently I think all builders are Fedora 36.
Okay, I tried to reproduce this environment with the mock in Fedora 36
and the fedora-rawhide-x86_64 configuration. This tester:
....snip...
This looks very good, no problematic EPERM errors. So I don't expect
this type of system call compatibility issues from the switch.
Great! thanks for testing. I seem to dimly recall that glibc was
something that nspawn broke before, but like I said, it was only right
after it landed that it was even attempted.
Since everyone seems postivie on this, I'll look at switching it on
monday and see what breaks.
kevin