If you're trying to access the build daemon from inside the package build
container, that must mean you have a derivation you're trying to build. Instead
of trying to circumvent the container (which is there for a reason), you could:
- write a bit of Scheme code that returns that derivation
- pass the result as an input.
That way, you build that derivation outside the build environment, and you can
refer to the result inside the build environment.
Le 2 août 2022 17:36:19 GMT+02:00, Olivier Dion via <help-guix@gnu.org> a écrit
:
>On Tue, 02 Aug 2022, "(" <pa...@disroot.org> wrote:
>> On Tue Aug 2, 2022 at 2:41 PM BST, Olivier Dion wrote:
>>> There seems to be an issue after all. When building with Guix, my
>>> script failed to access /var/guix/daemon-socket/socket with `guix
>>> shell'. I guess there's probably some way to make it available for the
>>> build?
>> You're in a container with access to nothing but the store and /tmp. It's
>> not surprising that trying to access anything else doesn't work.
>
>Right that was my though. Do you thin there is a way to expose the
>required files to the build container for accessing the Guix daemon?
>
>I have at least another case -- a guix+guile declarative build system --
>where I need to communicate with the Guix daemon in the build
>container.
>
>--
>Olivier Dion
>oldiob.dev
>
