[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guix Docker image inflation

From: zimoun
Subject: Re: Guix Docker image inflation
Date: Sun, 31 May 2020 11:08:39 +0200

Hi Chris,

On Sun, 31 May 2020 at 06:32, Chris Marusich <> wrote:

> I would guess that the size difference between A and B is approximately
> the same as the difference between A and C.  It'll be different, of
> course, but generally the size difference between A and C should not
> grow linearly with time, since "guix pull" is only going to install at
> most the total closure of things necessary to build and run Guix, which
> doesn't increase much in size as time goes on.  However, when you
> daisy-chain the images every day, the image size will grow linearly with
> time because the contents of all the previous layers is carried forward.

Exactly and it is not specific to Guix but it is how Docker works, if
I understand correctly.

> - Your script runs "docker commit" while guix-daemon (and other
>   programs) are still running.  To ensure the guix-daemon's database (or
>   other things) does not become corrupt, consider terminating all
>   processes before committing the new image.

Do you think the GC issue comes from this?
Because "docker stop" and then "docker commit" does not change the
issue.  The GC is still confused by trying to delete items than are
not in the store.  Roughly speaking, "guix gc" says it removes items
of size 0, but then "guix gc --references" says the path does not

--8<---------------cut here---------------start------------->8---
/ # /root/.config/guix/current/bin/guix gc
/root/.config/guix/current/bin/guix gc
/ # /root/.config/guix/current/bin/guix gc --list-dead | grep hello
/root/.config/guix/current/bin/guix gc --list-dead | grep hello
finding garbage collector roots...
determining live/dead paths...
/ # /root/.config/guix/current/bin/guix gc --references
/root/.config/guix/current/bin/guix gc --references
guix gc: error: path
`/gnu/store/kg9mirg6xbvzcp0a98v7326n1nvvwgsj-hello-2.10' is not valid
--8<---------------cut here---------------end--------------->8---

> I apologize for not reading your thread more closely to begin with.  I
> took a closer looks, and I think I can explain what is going on now.
> Please check the bug report and reply there if anything is unclear.

Ah sorry, maybe you always addressed these questions in the bug report.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]