From: Ryan Prior <ryanprior@hey.com>
To: "Danny Milosavljevic" <dannym@scratchpost.org>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: Development of GNU Guix and the GNU System distribution
<guix-devel@gnu.org>
Subject: Re: /etc/passwd & co. in Docker images
Date: Fri, 20 Nov 2020 18:53:14 +0000 [thread overview]
Message-ID: <3eb256f1afb57ad0636b610deeab49278dd56a83@hey.com> (raw)
In-Reply-To: <874klkfej4.fsf_-_@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On November 20, 2020, "Ludovic Courtès" <ludo@gnu.org> wrote:
> … what you’re doing here suggest that ‘guix pack’ should indeed create
> those files.
Oh I think it should be an option. Many Docker containers do not need
those things, but it would be great to have the option to include them.
Another option that would be nice, for the sake of `guix deploy` and
`guix pack`, is to produce a static build. I've tried adjusting some
Guix packages to produce static builds and seen dramatic reduction in
bundle sizes. I've brought up those observations in IRC and from those
convos I know most people aren't interested in static builds, but for
deployments to a cluster, a tiny container image with a single static
binary in it can be just the thing you want. This maybe plays into the
"parametric packages" thread that's happening in parallel, because I
could see offering this as a "static?" parameter on packages that
support it.
[-- Attachment #2: Type: text/html, Size: 3297 bytes --]
next prev parent reply other threads:[~2020-11-20 18:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 9:51 Releasing guix binary in Docker format too? Danny Milosavljevic
2020-09-23 11:07 ` Pjotr Prins
2020-09-23 12:53 ` zimoun
2020-09-24 7:59 ` Danny Milosavljevic
2020-10-20 10:29 ` zimoun
2020-10-21 9:12 ` Ludovic Courtès
2020-10-21 10:57 ` zimoun
2020-10-21 15:42 ` Ludovic Courtès
2020-11-04 14:43 ` Danny Milosavljevic
2020-11-06 9:59 ` Ludovic Courtès
2020-11-06 12:47 ` zimoun
2020-11-06 13:28 ` Danny Milosavljevic
2020-11-08 17:33 ` Ludovic Courtès
2020-11-15 18:30 ` zimoun
2020-11-17 16:38 ` Danny Milosavljevic
2020-11-18 12:56 ` Bengt Richter
2020-11-18 13:52 ` Ryan Prior
2020-11-18 14:25 ` zimoun
2020-10-21 11:04 ` Size of package 'guix' zimoun
2020-10-21 15:44 ` Ludovic Courtès
2020-10-21 16:04 ` zimoun
2020-11-04 11:05 ` Release: Docker Image? DockerHub? skopeo? zimoun
2020-11-04 13:44 ` Jelle Licht
2020-11-04 14:50 ` Danny Milosavljevic
2020-11-15 21:30 ` zimoun
2020-11-17 16:31 ` Danny Milosavljevic
2020-11-17 16:50 ` Danny Milosavljevic
2020-11-17 17:30 ` zimoun
2020-11-17 19:23 ` Danny Milosavljevic
2020-11-17 19:28 ` Danny Milosavljevic
2020-11-17 21:44 ` Ryan Prior
2020-11-17 22:05 ` Carlo Zancanaro
2020-11-19 9:21 ` zimoun
2020-11-19 10:49 ` Danny Milosavljevic
2020-11-20 11:34 ` /etc/passwd & co. in Docker images Ludovic Courtès
2020-11-20 18:53 ` Ryan Prior [this message]
2020-11-22 16:00 ` Danny Milosavljevic
2020-11-22 16:49 ` Ryan Prior
2020-11-29 12:51 ` Danny Milosavljevic
2020-12-05 15:08 ` Ludovic Courtès
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=3eb256f1afb57ad0636b610deeab49278dd56a83@hey.com \
--to=ryanprior@hey.com \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).