Richard Purdie <richard.purdie@linuxfoundation.org> escreveu no dia quarta,
19/01/2022 à(s) 23:27:

> On Wed, 2022-01-19 at 23:16 +0000, Jose Quaresma wrote:
> > Unfortunately this patch breaks the usage of the icecc.bbclass.
> >
> > Currently I build with icecc inside a container with network isolation
> and
> > my icecc demon runs outside of the container.
> > The only thing I need to do for using the icecc inside my build
> container is
> > mounting the unix /var/run/icecc/iceccd.socket inside the container.
> >
> > I think that we need something like this functionality to have access to
> > some sockets connections inside the tasks with the new namespace.
>
> I'm open to proposals but the unshare functionality is limited so I
> suspect we
> can't just allow/disallow specific sockets unfortunately. We may just need
> the
> global "allow" flag for the reasons Robert mentioned which would also work
> here,
> at the code of not showing up other network accesses.
>
> Cheers,
>
> Richard
>
>
I will do some more investigation on that to see how we can use some
pre-existing unix sockets from the old namespace.
I think that the IPC namespace is used for that purpose but I need to
understand more about this subject.

-- 
Best regards,

José Quaresma