From: ludo@gnu.org (Ludovic Courtès)
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 33171-done@debbugs.gnu.org
Subject: bug#33171: TMPDIR and build containers
Date: Thu, 01 Nov 2018 16:09:02 +0100 [thread overview]
Message-ID: <87efc4u969.fsf@gnu.org> (raw)
In-Reply-To: <20181027012336.glawlvz63m6kiiuu@florianbeaglebone.fritz.box> (pelzflorian's message of "Sat, 27 Oct 2018 03:23:36 +0200")
Hello Florian,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> The manual says that TMPDIR does not leak into the build environment:
>
>> You can influence the directory where the daemon stores build trees
>> via the ‘TMPDIR’ environment variable. However, the build tree within
>> the chroot is always called ‘/tmp/guix-build-NAME.drv-0’, where NAME is
>> the derivation name—e.g., ‘coreutils-8.24’. This way, the value of
>> ‘TMPDIR’ does not leak inside build environments, which avoids
>> discrepancies in cases where build processes capture the name of their
>> build tree.
>
>
> However, later it says:
>
>> When the daemon performs a build on behalf of the user, it creates a
>> build directory under ‘/tmp’ or under the directory specified by its
>> ‘TMPDIR’ environment variable; this directory is shared with the
>> container for the duration of the build. Be aware that using a
>> directory other than ‘/tmp’ can affect build results—for example, with a
>> longer directory name, a build process that uses Unix-domain sockets
>> might hit the name length limitation for ‘sun_path’, which it would
>> otherwise not hit.
>
>
> This seems like a contradiction, or do I misunderstand?
Indeed. The sentences that starts with “Be aware” is inaccurate; I’ll
remove it.
Thank you!
Ludo’.
prev parent reply other threads:[~2018-11-01 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 1:23 bug#33171: TMPDIR and build containers pelzflorian (Florian Pelz)
2018-11-01 15:09 ` Ludovic Courtès [this message]
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=87efc4u969.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33171-done@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).