When a delta image is pulled in the case that --delta-data-root (and other flags required for this) are set, the pull doesn't seem to succeed with the error:
unexpected EOF. Invalid delta tar archive
Steps to reproduce the issue:
start the balena daemon up with a single base folder: balenad --debug --data-root=$(pwd)/base/balena
create an image (pull in some base image, and just add an extra file, for example)
create a delta between this image and the base image used, tag it, push the image to Docker HUB
stop balena daemon, and restart with a separate delta data root pointing to the previous folder, and a new folder for the data root, such as balenad --delta-data-root=$(pwd)/base/balena --delta-storage-driver=overlay2 --data-root=$(pwd)/top/balena (the correct --delta-storage-driver is needed too)
check that balena now does not report the image (full or delta) in balena images
try to pull the delta pushed earlier
Describe the results you received:
The pull fails with unexpected EOF. Invalid delta tar archive:
debian-delta: Pulling from imrehg/deltatest
4f4fb700ef54: Pull complete
1c74fe47e344: Ready to download
Total: [========> ] 32B/187B
unexpected EOF. Invalid delta tar archive
In the daemon (run with --debug) on the first pull attempt this is the message:
DEBU[2018-08-30T12:35:21.066313192+01:00] Calling POST /v1.35/images/create?fromImage=imrehg%2Fdeltatest&tag=debian-delta
DEBU[2018-08-30T12:35:21.066492990+01:00] Trying to pull imrehg/deltatest from https://registry-1.docker.io v2
DEBU[2018-08-30T12:35:22.784842683+01:00] Pulling ref from V2 registry: imrehg/deltatest:debian-delta
DEBU[2018-08-30T12:35:23.612414067+01:00] pulling blob "sha256:1c74fe47e344589fc1b99d785a44faf71c512bc0aaad2dd71725e887f95b60f1"
DEBU[2018-08-30T12:35:23.612535111+01:00] pulling blob "sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1"
DEBU[2018-08-30T12:35:24.277139459+01:00] Applying tar in /home/greg/resin/balenadelta/top/balena/overlay2/8ceed3d52c471f8b60da6d070393889931be3af02b3616eea61f728d3af2b94a/diff
DEBU[2018-08-30T12:35:24.371635601+01:00] Applied tar sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 to 8ceed3d52c471f8b60da6d070393889931be3af02b3616eea61f728d3af2b94a, size: 0
INFO[2018-08-30T12:35:24.474578354+01:00] Attempting next endpoint for pull after error: unexpected EOF. Invalid delta tar archive
INFO[2018-08-30T12:35:24.478186653+01:00] Layer sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 cleaned up
Describe the results you expected:
I'd expect the pull to succeeds, similarly how it works without separate delta root, which is:
Description
When a delta image is pulled in the case that
--delta-data-root
(and other flags required for this) are set, the pull doesn't seem to succeed with the error:Steps to reproduce the issue:
balenad --debug --data-root=$(pwd)/base/balena
balenad --delta-data-root=$(pwd)/base/balena --delta-storage-driver=overlay2 --data-root=$(pwd)/top/balena
(the correct--delta-storage-driver
is needed too)balena images
Describe the results you received:
The pull fails with
unexpected EOF. Invalid delta tar archive
:In the daemon (run with
--debug
) on the first pull attempt this is the message:Describe the results you expected:
I'd expect the pull to succeeds, similarly how it works without separate delta root, which is:
Additional information you deem important (e.g. issue happens only occasionally):
overlay2
andaufs
graphdriversOutput of
balena version
:Output of
balena info
:balena info
when not running with a separate delta data root:balena info
when running with--delta-data-root
etc:Additional environment details (AWS, VirtualBox, physical, etc.):
Tested on ArchLinux, as well as ResinOS 2.14.3 (Intel NUC and Raspberry Pi 3)