large image problem
See original GitHub issue$ docker-squash -t beje:squash --output-path=squashed.tar 080bff34ab92
2016-09-13 13:50:08,222 root INFO docker-squash version 1.0.4, Docker 20f81dde, API 1.22...
2016-09-13 13:50:08,222 root INFO Using v2 image format
2016-09-13 13:50:08,245 root INFO Old image has 12 layers
2016-09-13 13:50:08,245 root INFO Checking if squashing is necessary...
2016-09-13 13:50:08,245 root INFO Attempting to squash last 12 layers...
2016-09-13 13:50:08,245 root INFO Saving image sha256:080bff34ab92e8dd804525ae6f4bb9ebbf76f45ab6ed7f468ebe948445cd2a47 to /tmp/docker-squash-I4MoyD/old/image.tar file...
2016-09-13 13:55:50,625 root INFO Image saved!
2016-09-13 13:55:50,625 root INFO Unpacking /tmp/docker-squash-I4MoyD/old/image.tar tar file to /tmp/docker-squash-I4MoyD/old directory
2016-09-13 13:58:03,609 root INFO Archive unpacked!
2016-09-13 13:58:04,407 root INFO Squashing image '080bff34ab92'...
2016-09-13 13:58:04,411 root INFO Starting squashing...
2016-09-13 13:58:04,411 root INFO Squashing file '/tmp/docker-squash-I4MoyD/old/a81e9bf57d57ea77b61ddd6078a675609748fa1a0e27046b067694bb2d347e67/layer.tar'...
2016-09-13 13:59:18,902 root INFO Squashing file '/tmp/docker-squash-I4MoyD/old/50f18a55ae51b71140e5d709d16170d608ef0944994bb256251b0946215e3e02/layer.tar'...
2016-09-13 13:59:18,904 root INFO Squashing file '/tmp/docker-squash-I4MoyD/old/93be9be73543462ed80ad539aec8b0fe43da0da32abdab2efbf1af525e941db5/layer.tar'...
2016-09-13 13:59:18,904 root INFO Squashing file '/tmp/docker-squash-I4MoyD/old/0e95a2283be05512286b3d88444cfb2010c669c5bf8bcdf4e738a12b89a33b6a/layer.tar'...
2016-09-13 13:59:23,788 root INFO Squashing file '/tmp/docker-squash-I4MoyD/old/e1fd594cc6ca6175b8c510e3257351faab908ca550a0688e10e8dbd75912f843/layer.tar'...
2016-09-13 13:59:23,793 root INFO Squashing file '/tmp/docker-squash-I4MoyD/old/e3e47292aae8f37f287b4ecf0c98befd42c7e05a27a75e296f28e3f21a04439d/layer.tar'...
2016-09-13 13:59:23,795 root INFO Squashing file '/tmp/docker-squash-I4MoyD/old/030c0db7e089abcd66da31ca1c24683d96ff389e8e0513f46b61089274de6620/layer.tar'...
2016-09-13 13:59:23,798 root INFO Squashing file '/tmp/docker-squash-I4MoyD/old/e325acda64892aad2067c23b10d39e4e6043f3dc38a316457818a2ff1f8dd586/layer.tar'...
2016-09-13 13:59:23,808 root INFO Squashing file '/tmp/docker-squash-I4MoyD/old/e35f039b56649ff8fd0636935f35a7c3ff567e6647b1412e96888dd339799c65/layer.tar'...
2016-09-13 13:59:32,463 root INFO Squashing finished!
2016-09-13 14:00:36,797 root INFO New squashed image ID is 8d076e26fed04347224890b20f3f80ac6a1281642f047f822d2859039f441ac9
2016-09-13 14:01:41,498 root INFO Image available at 'squashed.tar'
2016-09-13 14:03:22,072 root ERROR 500 Server Error: Internal Server Error ("Untar re-exec error: exit status 1: output: archive/tar: invalid tar header")
2016-09-13 14:03:22,073 root ERROR Execution failed, consult logs above. If you think this is our fault, please file an issue: https://github.com/goldmann/docker-squash/issues, thanks!
$ cat squashed.tar | docker load
Error response from daemon: Untar re-exec error: exit status 1: output: archive/tar: invalid tar header
$ journalctl -fu docker
Sep 13 14:38:30 matej71 docker[24431]: time="2016-09-13T14:38:30.660858614+02:00" level=error msg="Handler for POST /v1.22/images/load returned error: Untar re-exec error: exit status 1: output: archive/tar: invalid tar header"
$ docker images -a
# naturally there is no trace of image
- this is not the problem of not enough disk space - over 100GB free at the time of running these commands
- docker version is 1.10.3
- the original image is over 26GB, squashed image is 13GB
- if I repeat the process with a smaller image (~150MB), works as expected
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
The Great Big Image Problem - Webmentor
Your website is getting bigger and bigger. It's taking forever to backup. Ever wonder why? Chances are you're suffering from the Great Big ......
Read more >Most Common Issues with Image Sizes & How to Solve Them
In this article, we will cover the most common issues with Image Sizes and Videos in WordPress and how to solve them!
Read more >How to fix: Image too big - Google Merchant Center Help
Use an image that has a resolution of less than 64 megapixels and file size smaller than 16MBYou submitted one or more images...
Read more >Silverlight's Big Image Problem (and What You Can Do About It)
The problem is that because Silverlight's BitmapImage class consumes massive amounts of memory (up to 40 or 50 MB per image for a...
Read more >How to Make Images Larger Without Losing Quality: Real Tests!
Learn to resize and make images larger without losing quality with the best tools for the job. We compare each enlarger with vigorous...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Not directly related… but I’ve had problems with
docker save,docker load,docker pullanddocker pushmultiGB docker images in general with errors verrrrry similar toMy gut thinks it’s not a docker-squash issue.
I need to find bigger filesystem to test this, it filled all my space up 😃