From: rendaw <7e9wc56emjakcm@s.rendaw.me>
To: 35359@debbugs.gnu.org
Subject: bug#35359: docker-image produces corrupt tar
Date: Sun, 21 Apr 2019 22:44:32 +0900 [thread overview]
Message-ID: <beefec16-3c6c-2625-eb01-24a228bba51c@s.rendaw.me> (raw)
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.
next reply other threads:[~2019-04-21 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 13:44 rendaw [this message]
2019-04-21 20:35 ` bug#35359: docker-image produces corrupt tar Ludovic Courtès
2019-04-22 11:55 ` rendaw
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=beefec16-3c6c-2625-eb01-24a228bba51c@s.rendaw.me \
--to=7e9wc56emjakcm@s.rendaw.me \
--cc=35359@debbugs.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).