From: rendaw <7e9wc56emjakcm@s.rendaw.me>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35359@debbugs.gnu.org
Subject: bug#35359: docker-image produces corrupt tar
Date: Mon, 22 Apr 2019 20:55:05 +0900 [thread overview]
Message-ID: <e7e6df72-6cac-cf1d-bb86-5ce5e41e7863@s.rendaw.me> (raw)
In-Reply-To: <87a7gj2j13.fsf@gnu.org>
On 4/22/19 5:35 AM, Ludovic Courtès wrote:
> Hi,
>
> rendaw <7e9wc56emjakcm@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
next prev parent reply other threads:[~2019-04-22 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 13:44 bug#35359: docker-image produces corrupt tar rendaw
2019-04-21 20:35 ` Ludovic Courtès
2019-04-22 11:55 ` rendaw [this message]
2019-04-22 12:06 ` Ricardo Wurmus
2019-04-22 14:35 ` rendaw
2019-04-22 16:10 ` Ricardo Wurmus
2019-04-22 16:53 ` rendaw
2019-04-22 17:12 ` Ricardo Wurmus
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=e7e6df72-6cac-cf1d-bb86-5ce5e41e7863@s.rendaw.me \
--to=7e9wc56emjakcm@s.rendaw.me \
--cc=35359@debbugs.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).