From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: bokr@bokr.com, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 46782@debbugs.gnu.org, bbb ee <blasforr@gmail.com>,
Simon Tournier <zimon.toutoune@gmail.com>
Subject: bug#46782: guix environment --expose options cannot be layered onto $PWD
Date: Mon, 13 Feb 2023 22:17:09 +0100 [thread overview]
Message-ID: <875yc5clka.fsf@jpoiret.xyz> (raw)
In-Reply-To: <20230207012404.GA3706@LionPure>
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
Hello everyone,
A quick strace shows that it's actually an ordering issue: /home/user is
mounted in the container after /home/user/tmp. The fix is pretty
simple, moving the cwd first, before the explicit --expose arguments.
I'm noticing that the --expose option creates an empty tmp folder in the
user's home in that case though, which I don't like, however I don't
think there's any better option. Patch following.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-02-13 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 21:12 bug#46782: guix environment --expose options cannot be layered onto $PWD Maxim Cournoyer
2022-11-23 14:24 ` bug#46782: bbb ee
2023-01-27 16:19 ` bug#46782: guix environment --expose options cannot be layered onto $PWD Maxim Cournoyer
2023-01-27 17:31 ` Simon Tournier
2023-02-06 21:54 ` Maxim Cournoyer
2023-02-07 1:24 ` bokr
2023-02-13 21:17 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-02-13 21:31 ` bug#46782: [PATCH] scripts: environment: Mount cwd before user specified --expose Josselin Poiret via Bug reports for GNU Guix
2023-03-07 2:23 ` bug#46782: guix environment --expose options cannot be layered onto $PWD Maxim Cournoyer
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=875yc5clka.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=46782@debbugs.gnu.org \
--cc=blasforr@gmail.com \
--cc=bokr@bokr.com \
--cc=dev@jpoiret.xyz \
--cc=maxim.cournoyer@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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).