Re: Tracking and inspecting how Guix changes over time

[Ricardo Wurmus]

Christopher Baines <address@hidden> writes:

>> For an automated system like this, it’s a bit different, so using a
>> container makes a lot of sense.  I’d suggest having an option directly
>> in (guix inferior) to allow users to choose whether to run an inferior
>> in separate name spaces.  WDYT?
>
> That sounds great, I'm not quite sure how to make it happen though...
>
> So inferior-pipe in (guix inferior) uses open-pipe*. The root of the
> Linux container code in Guix looks to be run-container (gnu build
> linux-container).

You can use “call-with-container”, which runs a thunk inside a container.

-- 
Ricardo