docker load for my image fails with “Error processing tar file(exit status 1): not a directory”
docker load -i myimg.tar.gz
19eb0038b177: Loading layer [========================>] 199.6MB/199.6MB
9ccc7116172f: Loading layer [========================>] 207.6MB/207.6MB
Error processing tar file(exit status 1): not a directory
I’m trying to copy over an existing Docker image running on my local server to another host using docker save. The compressed image is smaller than 400 MB.
file -b myimg.tar.gz
gzip compressed data, was "myimg.tar", last modified: Mon Nov 26 18:30:56 2018, max compression, from Unix
ls -l myimg.tar.gz
-rwxr-xr-x 1 ubuntu ubuntu 370401317 Nov 26 18:35 myimg.tar.gz
This happens with any image built for any of the micro services running within my application on my local server. It does not happen with other standard applications I pulled from public registries, such as HelloWorld, Nginx, ElasticSearch, Kafka etc. The error remains the same whether the TAR archive is compressed or not.
I can docker load the image from the generated TAR on my local server itself without any issues.
Is there a way to debug what happens internally when I run docker load ? Also, is there anything I can check for while opening up the docker image TAR for inspection?
docker --version
Docker version 18.09.0, build 4d60db4
The underlying OS is Ubuntu 18.04.
docker
edited Nov 26 '18 at 20:03
David Maze
13.8k31327
asked Nov 26 '18 at 19:59
jugulatorjugulator
11
add a comment |
docker load -i myimg.tar.gz
19eb0038b177: Loading layer [========================>] 199.6MB/199.6MB
9ccc7116172f: Loading layer [========================>] 207.6MB/207.6MB
Error processing tar file(exit status 1): not a directory
I’m trying to copy over an existing Docker image running on my local server to another host using docker save. The compressed image is smaller than 400 MB.
file -b myimg.tar.gz
gzip compressed data, was "myimg.tar", last modified: Mon Nov 26 18:30:56 2018, max compression, from Unix
ls -l myimg.tar.gz
-rwxr-xr-x 1 ubuntu ubuntu 370401317 Nov 26 18:35 myimg.tar.gz
This happens with any image built for any of the micro services running within my application on my local server. It does not happen with other standard applications I pulled from public registries, such as HelloWorld, Nginx, ElasticSearch, Kafka etc. The error remains the same whether the TAR archive is compressed or not.
I can docker load the image from the generated TAR on my local server itself without any issues.
Is there a way to debug what happens internally when I run docker load ? Also, is there anything I can check for while opening up the docker image TAR for inspection?
docker --version
Docker version 18.09.0, build 4d60db4
The underlying OS is Ubuntu 18.04.
docker
edited Nov 26 '18 at 20:03
David Maze
13.8k31327
asked Nov 26 '18 at 19:59
jugulatorjugulator
11
add a comment |
docker load -i myimg.tar.gz
19eb0038b177: Loading layer [========================>] 199.6MB/199.6MB
9ccc7116172f: Loading layer [========================>] 207.6MB/207.6MB
Error processing tar file(exit status 1): not a directory
I’m trying to copy over an existing Docker image running on my local server to another host using docker save. The compressed image is smaller than 400 MB.
file -b myimg.tar.gz
gzip compressed data, was "myimg.tar", last modified: Mon Nov 26 18:30:56 2018, max compression, from Unix
ls -l myimg.tar.gz
-rwxr-xr-x 1 ubuntu ubuntu 370401317 Nov 26 18:35 myimg.tar.gz
This happens with any image built for any of the micro services running within my application on my local server. It does not happen with other standard applications I pulled from public registries, such as HelloWorld, Nginx, ElasticSearch, Kafka etc. The error remains the same whether the TAR archive is compressed or not.
I can docker load the image from the generated TAR on my local server itself without any issues.
Is there a way to debug what happens internally when I run docker load ? Also, is there anything I can check for while opening up the docker image TAR for inspection?
docker --version
Docker version 18.09.0, build 4d60db4
The underlying OS is Ubuntu 18.04.
docker
edited Nov 26 '18 at 20:03
David Maze
13.8k31327
asked Nov 26 '18 at 19:59
jugulatorjugulator
11
docker load -i myimg.tar.gz
19eb0038b177: Loading layer [========================>] 199.6MB/199.6MB
9ccc7116172f: Loading layer [========================>] 207.6MB/207.6MB
Error processing tar file(exit status 1): not a directory
I’m trying to copy over an existing Docker image running on my local server to another host using docker save. The compressed image is smaller than 400 MB.
file -b myimg.tar.gz
gzip compressed data, was "myimg.tar", last modified: Mon Nov 26 18:30:56 2018, max compression, from Unix
ls -l myimg.tar.gz
-rwxr-xr-x 1 ubuntu ubuntu 370401317 Nov 26 18:35 myimg.tar.gz
This happens with any image built for any of the micro services running within my application on my local server. It does not happen with other standard applications I pulled from public registries, such as HelloWorld, Nginx, ElasticSearch, Kafka etc. The error remains the same whether the TAR archive is compressed or not.
I can docker load the image from the generated TAR on my local server itself without any issues.
Is there a way to debug what happens internally when I run docker load ? Also, is there anything I can check for while opening up the docker image TAR for inspection?
docker --version
Docker version 18.09.0, build 4d60db4
The underlying OS is Ubuntu 18.04.
docker
docker
edited Nov 26 '18 at 20:03
David Maze
13.8k31327
asked Nov 26 '18 at 19:59
jugulatorjugulator
11
edited Nov 26 '18 at 20:03
David Maze
13.8k31327
asked Nov 26 '18 at 19:59
jugulatorjugulator
11
edited Nov 26 '18 at 20:03
David Maze
13.8k31327
edited Nov 26 '18 at 20:03
David Maze
13.8k31327
edited Nov 26 '18 at 20:03
David Maze
13.8k31327
13.8k31327
asked Nov 26 '18 at 19:59
jugulatorjugulator
11
asked Nov 26 '18 at 19:59
jugulatorjugulator
11
asked Nov 26 '18 at 19:59
jugulatorjugulator
11
11
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53488146%2fdocker-load-for-my-image-fails-with-error-processing-tar-fileexit-status-1-n%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53488146%2fdocker-load-for-my-image-fails-with-error-processing-tar-fileexit-status-1-n%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
