From: Ricardo Wurmus <rekado@elephly.net>
To: Caleb Ristvedt <caleb.ristvedt@cune.org>
Cc: guix-devel@gnu.org
Subject: Re: Latest guile-daemon changes and bewilderment
Date: Sun, 20 Aug 2017 08:30:35 +0200 [thread overview]
Message-ID: <87y3qewy2c.fsf@elephly.net> (raw)
In-Reply-To: <87wp6sbygq.fsf@cune.org>
Hi,
> There are a couple of issues with using call-with-container. In
> decreasing order of perceived difficulty to solve:
>
> 1. Copying the output from the build to the real store. How would that
> work? It wouldn't work with call-with-container - the container can't
> access the outside world, and the chroot directory is automatically
> deleted once the scope of the container is left.
The usual way to deal with this is to bind mount outside directories
into a local directory in the container. Have you tried that or is this
not applicable?
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-08-20 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 10:18 Latest guile-daemon changes and bewilderment Caleb Ristvedt
2017-07-25 8:44 ` Ludovic Courtès
2017-07-28 11:19 ` Caleb Ristvedt
2017-08-01 12:46 ` Ludovic Courtès
2017-08-20 6:30 ` Ricardo Wurmus [this message]
2017-07-25 20:05 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3qewy2c.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=caleb.ristvedt@cune.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).