GNU bug report logs - #35359
docker-image produces corrupt tar

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35359 in the body.
You can then email your comments to 35359 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
To: submit <at> debbugs.gnu.org
Subject: docker-image produces corrupt tar
Date: Sun, 21 Apr 2019 22:44:32 +0900

Package: guix
Version: 0.16.0

I took the sample system configuration at the top of
https://www.gnu.org/software/guix/manual/en/html_node/Using-the-Configuration-System.html#Using-the-Configuration-System
and ran:

```
$ guix system docker-image testsystem2.scm --on-error=backtrace
successfully built
/gnu/store/l3psqh73xjb5h11y1hwrlfvl1yr920x4-guixsd-docker-image.tar.gz.drv
/gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz
$ tar -ztf
/gnu/store/d8rr8ilwm7l0xjachp7glbhp9qf4hjyg-guixsd-docker-image.tar.gz ^C
$ docker load <
/gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz
Error processing tar file(exit status 1): unexpected EOF
$ tar -ztf
/gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz
./
./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/
./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/VERSION
./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/json
./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/layer.tar

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
```

Qemu (?) clears my scroll history but I don't see any errors or warnings
from that point on.

My system is pretty typical - x86 Arch Linux with standard core binaries
and such.

Message #8 received at 35359 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
Cc: 35359 <at> debbugs.gnu.org
Subject: Re: bug#35359: docker-image produces corrupt tar
Date: Sun, 21 Apr 2019 22:35:52 +0200

Hi,

rendaw <7e9wc56emjakcm <at> s.rendaw.me> skribis:

> $ guix system docker-image testsystem2.scm --on-error=backtrace
> successfully built
> /gnu/store/l3psqh73xjb5h11y1hwrlfvl1yr920x4-guixsd-docker-image.tar.gz.drv
> /gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz
> $ tar -ztf
> /gnu/store/d8rr8ilwm7l0xjachp7glbhp9qf4hjyg-guixsd-docker-image.tar.gz ^C
> $ docker load <
> /gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz
> Error processing tar file(exit status 1): unexpected EOF
> $ tar -ztf
> /gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz
> ./
> ./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/
> ./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/VERSION
> ./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/json
> ./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/layer.tar
>
> gzip: stdin: unexpected end of file
> tar: Unexpected EOF in archive
> tar: Error is not recoverable: exiting now
> ```

What’s the output of ‘guix describe’?

This problem was initially fixed in
0dc7d298a33f83d5f02a962b5f1bd24ee0e8ef07 (March 22), with a followup in
66ec389580d4f1e4b81e1c72afe2749a547a0e7ca (Apr. 14).

Thanks,
Ludo’.

Message #11 received at 35359 <at> debbugs.gnu.org (full text, mbox):

From: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 35359 <at> debbugs.gnu.org
Subject: Re: bug#35359: docker-image produces corrupt tar
Date: Mon, 22 Apr 2019 20:55:05 +0900

On 4/22/19 5:35 AM, Ludovic Courtès wrote:
> Hi,
>
> rendaw <7e9wc56emjakcm <at> s.rendaw.me> skribis:
>
>> $ guix system docker-image testsystem2.scm --on-error=backtrace
>> successfully built
>> /gnu/store/l3psqh73xjb5h11y1hwrlfvl1yr920x4-guixsd-docker-image.tar.gz.drv
>> /gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz
>> $ tar -ztf
>> /gnu/store/d8rr8ilwm7l0xjachp7glbhp9qf4hjyg-guixsd-docker-image.tar.gz ^C
>> $ docker load <
>> /gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz
>> Error processing tar file(exit status 1): unexpected EOF
>> $ tar -ztf
>> /gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz
>> ./
>> ./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/
>> ./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/VERSION
>> ./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/json
>> ./41bc17c3316805da9a209f5835327160c8993ab4311c9cb649911a4ae41d1603/layer.tar
>>
>> gzip: stdin: unexpected end of file
>> tar: Unexpected EOF in archive
>> tar: Error is not recoverable: exiting now
>> ```
> What’s the output of ‘guix describe’?
>
> This problem was initially fixed in
> 0dc7d298a33f83d5f02a962b5f1bd24ee0e8ef07 (March 22), with a followup in
> 66ec389580d4f1e4b81e1c72afe2749a547a0e7ca (Apr. 14).
>
> Thanks,
> Ludo’.
$ guix describe
guix describe: error: failed to determine origin

$ guix --version
guix (GNU Guix) 0.16.0
Copyright (C) 2018 the Guix authors
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

I tried `guix describe` as root too, same error.

I downloaded guix a couple weeks ago, so it's possible it's out of
date.  It looks like the same version as is listed on the website though.

Cheers,

rendaw

Message #14 received at 35359 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 35359 <at> debbugs.gnu.org
Subject: Re: bug#35359: docker-image produces corrupt tar
Date: Mon, 22 Apr 2019 14:06:37 +0200

rendaw <7e9wc56emjakcm <at> s.rendaw.me> writes:

> $ guix --version
> guix (GNU Guix) 0.16.0
> Copyright (C) 2018 the Guix authors
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> I tried `guix describe` as root too, same error.
>
> I downloaded guix a couple weeks ago, so it's possible it's out of
> date. It looks like the same version as is listed on the website though.

This is the last release, but you should run “guix pull” on a regular
basis to get updates to Guix and to be able to install package updates.

--
Ricardo

Message #17 received at 35359 <at> debbugs.gnu.org (full text, mbox):

From: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 35359 <at> debbugs.gnu.org
Subject: Re: bug#35359: docker-image produces corrupt tar
Date: Mon, 22 Apr 2019 23:35:13 +0900

On 4/22/19 9:06 PM, Ricardo Wurmus wrote:
> rendaw <7e9wc56emjakcm <at> s.rendaw.me> writes:
>
>> $ guix --version
>> guix (GNU Guix) 0.16.0
>> Copyright (C) 2018 the Guix authors
>> License GPLv3+: GNU GPL version 3 or later
>> <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>>
>> I tried `guix describe` as root too, same error.
>>
>> I downloaded guix a couple weeks ago, so it's possible it's out of
>> date. It looks like the same version as is listed on the website though.
> This is the last release, but you should run “guix pull” on a regular
> basis to get updates to Guix and to be able to install package updates.
>
> --
> Ricardo
>
Thanks!  I just did `guix pull` and forced an image rebuild (by changing
host-name), but I get the same tar error.

Message #20 received at 35359 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 35359 <at> debbugs.gnu.org
Subject: Re: bug#35359: docker-image produces corrupt tar
Date: Mon, 22 Apr 2019 18:10:46 +0200

rendaw <7e9wc56emjakcm <at> s.rendaw.me> writes:

> Thanks! I just did `guix pull` and forced an image rebuild (by changing
> host-name)

Changing the host name is not needed.  After getting the new Guix most
of the packages that should end up in the image would be updated
anyway.

> but I get the same tar error.

I’m guessing that you are not actually using the pulled Guix because
your shell may have cached the former location of the “guix”
executable.  Please try again with ~/.config/guix/current/bin/guix
instead of just “guix”.

You can also run “hash guix” in Bash to invalidate the cache.

-- 
Ricardo

Message #23 received at 35359 <at> debbugs.gnu.org (full text, mbox):

From: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 35359 <at> debbugs.gnu.org
Subject: Re: bug#35359: docker-image produces corrupt tar
Date: Tue, 23 Apr 2019 01:53:50 +0900

On 4/23/19 1:10 AM, Ricardo Wurmus wrote:
> rendaw <7e9wc56emjakcm <at> s.rendaw.me> writes:
>
>> Thanks! I just did `guix pull` and forced an image rebuild (by changing
>> host-name)
> Changing the host name is not needed.  After getting the new Guix most
> of the packages that should end up in the image would be updated
> anyway.
>
>> but I get the same tar error.
> I’m guessing that you are not actually using the pulled Guix because
> your shell may have cached the former location of the “guix”
> executable.  Please try again with ~/.config/guix/current/bin/guix
> instead of just “guix”.
>
> You can also run “hash guix” in Bash to invalidate the cache.
Thanks, that was the issue.  I replaced the path and now the build uses
fresh packages and the tar is not corrupt.  This can be closed.

Message #28 received at 35359-done <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 35359-done <at> debbugs.gnu.org
Subject: Re: bug#35359: docker-image produces corrupt tar
Date: Mon, 22 Apr 2019 19:12:05 +0200

rendaw <7e9wc56emjakcm <at> s.rendaw.me> writes:

> On 4/23/19 1:10 AM, Ricardo Wurmus wrote:
>> rendaw <7e9wc56emjakcm <at> s.rendaw.me> writes:
>>
>>> Thanks! I just did `guix pull` and forced an image rebuild (by changing
>>> host-name)
>> Changing the host name is not needed.  After getting the new Guix most
>> of the packages that should end up in the image would be updated
>> anyway.
>>
>>> but I get the same tar error.
>> I’m guessing that you are not actually using the pulled Guix because
>> your shell may have cached the former location of the “guix”
>> executable.  Please try again with ~/.config/guix/current/bin/guix
>> instead of just “guix”.
>>
>> You can also run “hash guix” in Bash to invalidate the cache.
> Thanks, that was the issue. I replaced the path and now the build uses
> fresh packages and the tar is not corrupt. This can be closed.

Excellent.  Thanks for the confirmation!

Closing.

-- 
Ricardo

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.