From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Tropin <andrew@trop.in>
Cc: 54377@debbugs.gnu.org
Subject: [bug#54377] [PATCH 0/3] Add 'guix home container'
Date: Sat, 19 Mar 2022 11:39:17 +0100 [thread overview]
Message-ID: <87lex6ns4q.fsf_-_@gnu.org> (raw)
In-Reply-To: <87y216h6jc.fsf@trop.in> (Andrew Tropin's message of "Sat, 19 Mar 2022 08:09:59 +0300")
Hi,
Andrew Tropin <andrew@trop.in> skribis:
> What I meant by previous comment: to match a real state of the things
> it's better to use a shell from /etc/passwd, because it will be launched
> on user login and will read env vars and run all the following
> processes, but to make it more reproducible and independent from system
> state I think we always have to use hardcoded bash and inside the
> container inspect the value of $SHELL set by login shell (hardcoded
> bash) and spawn new shell if $SHELL is NOT empty.
Yeah, there’s a tension between conflicting criteria: independence from
system state, and faithful reproduction of what would happen on the
system. I feel like checking $SHELL is a middle ground.
I don’t know, we can revisit that as we gain more experience with the
tool I guess.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-03-19 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 21:52 [bug#54377] [PATCH 0/3] Add 'guix home container' Ludovic Courtès
2022-03-13 21:54 ` [bug#54377] [PATCH 1/3] linux-container: 'eval/container' honors #:namespaces Ludovic Courtès
2022-03-13 21:54 ` [bug#54377] [PATCH 2/3] linux-container: Add #:guest-uid and #:guest-gid to 'eval/container' Ludovic Courtès
2022-03-13 21:54 ` [bug#54377] [PATCH 3/3] guix home: Add 'container' command Ludovic Courtès
2022-03-17 6:24 ` Andrew Tropin
2022-03-18 13:25 ` Ludovic Courtès
2022-03-19 5:09 ` Andrew Tropin
2022-03-19 10:39 ` Ludovic Courtès [this message]
2022-03-19 15:03 ` [bug#54377] [PATCH 0/3] Add 'guix home container' Andrew Tropin
2022-03-19 18:24 ` bug#54377: " Ludovic Courtès
2022-03-17 15:01 ` [bug#54377] " Frank Pursel
2022-03-19 10:32 ` Ludovic Courtès
2022-03-23 3:06 ` Frank Pursel
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=87lex6ns4q.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=54377@debbugs.gnu.org \
--cc=andrew@trop.in \
/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).