https://bugzilla.redhat.com/show_bug.cgi?id=1140398
Bug ID: 1140398 Summary: Catastrophic failure saving large images Product: Fedora Version: 20 Component: docker-io Severity: medium Assignee: lsm5@fedoraproject.org Reporter: briemers@redhat.com QA Contact: extras-qa@fedoraproject.org CC: admiller@redhat.com, golang@lists.fedoraproject.org, hushan.jia@gmail.com, jperrin@centos.org, lsm5@fedoraproject.org, mattdm@redhat.com, mgoldman@redhat.com, s@shk.io, vbatts@redhat.com
Description of problem:
Large docker images are saved written first to temp. As such when one does a "docker save" for a large image the save process will error out with a disk full error. Afterwards, there will be mounting error if attempting to save the image again after resizing tmp.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce: 1. Create an image much larger than your /tmp space 2. Attempt to save 3.
Actual results:
[briemers@briemersw staging]$ docker save -o /data/oracle-xe-prod.dimg oracle-xe-prod 2014/09/10 16:41:23 Error: write /tmp/docker-export-336322967/dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38/layer.tar: no space left on device [briemers@briemersw staging]$ sudo mount -o remount,size=20g /tmp [sudo] password for briemers: [briemers@briemersw staging]$ docker save -o /data/oracle-xe-prod.dimg oracle-xe-prod 2014/09/10 16:43:25 Error: Error mounting '/dev/mapper/docker-253:2-2097434-dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38' on '/var/lib/docker/devicemapper/mnt/dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38': device or resource busy [briemers@briemersw staging]$ sudo service docker restart Redirecting to /bin/systemctl restart docker.service [briemers@briemersw staging]$ docker save -o /data/oracle-xe-prod.dimg oracle-xe-prod 2014/09/10 16:43:52 Error: Error mounting '/dev/mapper/docker-253:2-2097434-dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38' on '/var/lib/docker/devicemapper/mnt/dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38': device or resource busy
Expected results:
I would not expect the process to need massive amounts of /tmp space, if so it should have an option to specify where the tmp files are written. Also, the process needs to clean-up it's locks so subsiquent commands don't fail.
Additional info: