all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Pugnet <simon@polaris64.net>
To: Hilton Chain <hako@ultrarare.space>
Cc: help-guix@gnu.org
Subject: Re: guix pack: support for something similar to Nix's buildLayeredImage
Date: Thu, 10 Aug 2023 08:14:30 +0100	[thread overview]
Message-ID: <87v8dn4am3.fsf@polaris64.net> (raw)
In-Reply-To: <87350rpuw1.wl-hako@ultrarare.space>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

Hi Hilton,

Hilton Chain <hako@ultrarare.space> writes:

> Hi Simon,
>
> On Wed, 09 Aug 2023 20:59:02 +0800,
> Simon Pugnet wrote:
>>
>> I'm not a Guix or Nix expert but as far as I understand Nix solves
>> this problem by using "pkgs.dockerTools.buildLayeredImage" (see
>> http://ryantm.github.io/nixpkgs/builders/images/dockertools/#ssec-pkgs-dockerTools-buildLayeredImage)
>> and "streamLayeredImage". In this example, this could in theory be
>> used to build a coreutils-python image where coreutils exists in 
>> its
>> own layer. That would mean that the coreutils-rust image could 
>> share
>> the coreutils layer, saving space.
>>
>> Is there any way to achieve something similar in Guix? If not then 
>> are
>> there any plans to support this functionality?
>
> It's currently not available in Guix, but there's a patch series
> <https://issues.guix.gnu.org/62153> for it.
>
> Thanks

Excellent, thanks for pointing that out, and sorry for missing it in 
my searches!

Kind regards,

-- 
Simon Pugnet
https://www.polaris64.net/
PGP key fingerprint: 3BF7 85DE 162C 00C8 FB4D  A6FD BA13 59A8 2C0B 
3EF9

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

      reply	other threads:[~2023-08-10  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 12:59 guix pack: support for something similar to Nix's buildLayeredImage Simon Pugnet
2023-08-10  1:07 ` Hilton Chain
2023-08-10  7:14   ` Simon Pugnet [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8dn4am3.fsf@polaris64.net \
    --to=simon@polaris64.net \
    --cc=hako@ultrarare.space \
    --cc=help-guix@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 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.