From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 37162@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#37162: ‘guix pack -f docker’ creates an image without /etc/passwd
Date: Mon, 26 Aug 2019 13:39:40 +0200 [thread overview]
Message-ID: <87sgpoi29v.fsf@elephly.net> (raw)
In-Reply-To: <87y2zg2x7z.fsf@inria.fr>
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>> What use case(s) exactly depend on the presence of the
>> /etc/{passwd,group,shadow} files?
>
> Generally, absent these files, getpw(3) and co. won’t give useful
> results, and some applications will behave poorly (e.g., the PS1 prompt
> in Bash can’t show the user name; ‘id’ fails).
>
> Most of the time it’s just a minor inconvenience.
I think it’s fine to add these files to avoid this source of
inconvenience.
Perhaps it would be good to recommend in the manual the use of “guix
system” for those who need more control over the contents of these
files.
And maybe we can make some really simple template system configuration
available to “guix system” without requiring users to fully specify the
operating system configuration. I’m thinking of something like this
where %simple-os is made available by default:
(operating-system
(inherit %simple-os)
(packages (list "a" "b" "c")))
--
Ricardo
next prev parent reply other threads:[~2019-08-26 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 15:00 bug#37162: ‘guix pack -f docker’ creates an image without /etc/passwd Ludovic Courtès
2019-08-23 20:16 ` Ricardo Wurmus
2019-08-25 21:32 ` Maxim Cournoyer
2019-08-25 16:28 ` Ricardo Wurmus
2019-08-26 9:19 ` Maxim Cournoyer
2019-08-26 7:37 ` Ludovic Courtès
2019-08-26 11:39 ` Ricardo Wurmus [this message]
2019-08-31 15:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgpoi29v.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=37162@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=maxim.cournoyer@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.