Re: "guix pack -f docker" does too much work

2024-10-05 Thread Maxim Cournoyer
Hi, Simon Tournier writes: [...] >> Dependent on the situation I can see one approach to be preferrable to >> the other, and in other situations this could very well be reversed. > > I agree. Why not, if someone's itch is strong enough to implement it! >> Can we expose this choice to the comm

Re: "guix pack -f docker" does too much work

2024-09-14 Thread Ricardo Wurmus
Maxim Cournoyer writes: >>> I think it would be great if "guix pack -f docker" could avoid building >>> all these identical layers again and again. Perhaps it would be >>> possible to have a single derivation for each layer? This way we >>> wouldn't have to recreate the same layer archives ever

Re: "guix pack -f docker" does too much work

2024-06-17 Thread Ludovic Courtès
Hi, Michal Atlas skribis: >>> Also seems that Nix's way only quickly imports the changed layers? And >>> Guix's always imports the whole thing, at least I think? >> What do you mean by “imports the whole thing”? > > I'm not sure what exactly happens, so correct me if I'm wrong, however > if I ti

Re: "guix pack -f docker" does too much work

2024-06-17 Thread Michal Atlas
Hi, Also seems that Nix's way only quickly imports the changed layers? And Guix's always imports the whole thing, at least I think? What do you mean by “imports the whole thing”? I'm not sure what exactly happens, so correct me if I'm wrong, however if I time the different approaches, I think

Re: "guix pack -f docker" does too much work

2024-06-17 Thread Ludovic Courtès
Hi, Michal Atlas skribis: > I greatly agree, it would be an awesome QOL improvement. If there’s consensus, let’s see how we can get that done. The advantage of having (guix docker) & co. all in Scheme is that moving it from a derivation to code running straight from ‘guix pack’ is definitely f

Re: "guix pack -f docker" does too much work

2024-06-04 Thread Simon Tournier
Hi, On Sat, 01 Jun 2024 at 15:58, Ludovic Courtès wrote: >> I think it would be great if "guix pack -f docker" could avoid building >> all these identical layers again and again. Perhaps it would be >> possible to have a single derivation for each layer? This way we >> wouldn't have to recreat

Re: "guix pack -f docker" does too much work

2024-06-03 Thread Andy Wingo
On Sat 01 Jun 2024 15:58, Ludovic Courtès writes: >> I think it would be great if "guix pack -f docker" could avoid building >> all these identical layers again and again. Perhaps it would be >> possible to have a single derivation for each layer? This way we >> wouldn't have to recreate the sa

Re: "guix pack -f docker" does too much work

2024-06-02 Thread Michal Atlas
Hello Ricardo, I greatly agree, it would be an awesome QOL improvement. Just want to mention that it might be nice to take inspiration from the Nix dockerTools, since they already have quite a lot of effort put into this. Including for example an option called `streamLayeredImage` [1] which

Re: "guix pack -f docker" does too much work

2024-06-01 Thread Ricardo Wurmus
Ludovic Courtès writes: >> I think it would be great if "guix pack -f docker" could avoid building >> all these identical layers again and again. Perhaps it would be >> possible to have a single derivation for each layer? This way we >> wouldn't have to recreate the same layer archives every ti

"guix pack -f docker" does too much work

2024-05-29 Thread Ricardo Wurmus
Hi Guix, a few months ago "guix pack -f docker" was modified to produce layers. This is great! Unfortunately, "guix pack" itself still produces one big tarball containing all these layers. There is no sharing of previously built layers, because they are all hidden inside the pack. I think it wo