


It compresses the tar and makes it smaller in size. Solution: We can do it by using the gzip command. docker run -ti lsstsqre/centos:7-stack-lsst_distrib-w_2018_10ĭocker: failed to register layer: Error processing tar file(exit status 1): unexpected EOF.ġ44a9fa3d421: Extracting 511.7MB/511. Scenario: Save Docker images to a tar.gz file. Unable to find image 'lsstsqre/centos:7-stack-lsst_distrib-w_2018_10' locallyħ-stack-lsst_distrib-w_2018_10: Pulling from lsstsqre/centosĪ587006746df: Extracting 697.5MB/697.5MBĭocker: failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header. docker run -ti lsstsqre/centos:7-stack-lsst_distrib-w_2018_10
#Docker run image from tar install
I’m using the Docker for MacOSX app install to provide the command-line tools. docker image save suspect-image:latest >. This command saves an images data directly to a tar archive. I would love for a simple way to get a little more information to take to my local NOC, if the problem is on our end. Used a variation on this technique docker image save. I unfortunately have no ability to run useful things like traceroute or mtr from my machine (I can run them but the useful information is filtered out). Previous discussions on Slack with and on March 13 suggested this was a problem in the downloads from AWS and the real-time compression.

This morning I had my longest series of unsuccessful tries. kaniko is a tool to build container images from a Dockerfile, inside a. I have to try a few times before I get a successful clean download. I generally have trouble downloading a Docker image of the stack.
