FS#49484 - [docker] Save does not work

Attached to Project: Community Packages
Opened by Daniel Milde (dundee) - Friday, 27 May 2016, 12:44 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 06 June 2016, 15:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Docker save does not work for some unknown reason.

Additional info:

Client:
Version: 1.11.1
API version: 1.23
Go version: go1.6.2
Git commit: 5604cbe
Built: Mon May 2 00:06:51 2016
OS/Arch: linux/amd64

Server:
Version: 1.11.1
API version: 1.23
Go version: go1.6.2
Git commit: 5604cbe
Built: Mon May 2 00:06:51 2016
OS/Arch: linux/amd64

Containers: 2
Running: 0
Paused: 0
Stopped: 2
Images: 133
Server Version: 1.11.1
Storage Driver: devicemapper
Pool Name: docker-254:2-1194436-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: ext4
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 5.49 GB
Data Space Total: 107.4 GB
Data Space Available: 17 GB
Metadata Space Used: 7.602 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.14 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.124 (2016-05-07)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 4.5.4-1-ARCH
Operating System: Arch Linux
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.725 GiB
Name: dundee-dell
ID: 2YJ4:AJ2N:IXKF:BNW5:2POI:N5DK:HQZD:O2N2:25S7:PY6U:POMG:FDSV
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Username: dundee
Registry: https://index.docker.io/v1/

Steps to reproduce:

$ docker save debian:wheezy > debian.tar
Error response from daemon: unexpected EOF

Log:
14:25:16 systemd[16501]: dev-disk-by\x2duuid-5698f33f\x2d9b99\x2d44dd\x2db15e\x2d3f8f02d01af7.device: Dev dev-disk-by\x2duuid-5698f33f\x2d9b99\x2d44dd\x2db15e\x2d3f8f02d01af7.device appeared t
14:25:16 systemd[1]: dev-disk-by\x2duuid-5698f33f\x2d9b99\x2d44dd\x2db15e\x2d3f8f02d01af7.device: Dev dev-disk-by\x2duuid-5698f33f\x2d9b99\x2d44dd\x2db15e\x2d3f8f02d01af7.device appeared twice
14:25:16 systemd[955]: dev-disk-by\x2duuid-5698f33f\x2d9b99\x2d44dd\x2db15e\x2d3f8f02d01af7.device: Dev dev-disk-by\x2duuid-5698f33f\x2d9b99\x2d44dd\x2db15e\x2d3f8f02d01af7.device appeared twi
14:25:16 kernel: EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
14:25:18 docker[29145]: time="2016-05-27T14:25:18.396183514+02:00" level=error msg="Handler for GET /v1.23/images/get returned error: unexpected EOF"
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 06 June 2016, 15:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  containerd 0.2.2-1
Comment by Ike Devolder (BlackEagle) - Monday, 06 June 2016, 12:44 GMT
did you report this upstream?
Comment by Daniel Milde (dundee) - Monday, 06 June 2016, 13:12 GMT
Not yet, do you think I should?
I guessed is some error in Arch configs.
Comment by Ike Devolder (BlackEagle) - Monday, 06 June 2016, 14:24 GMT
I just tested it with 1.11.2 and it seems to work. So If you still have this issues you might need to check upstream. Or it was fixed in the newest version.
Comment by Daniel Milde (dundee) - Monday, 06 June 2016, 15:05 GMT
Yes, it now works with the new version of containerd. Please close. Thanks!

Loading...