Downloaded newer image - docker: Error response from daemon: OCI runtime create failed: container_linux.go:348:
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I want to download the busybox image and I get it but despite it I have the following error:
λ bgarcial [~] → sudo docker run busybox:1.29 "hello world"
Unable to find image 'busybox:1.29' locally
1.29: Pulling from library/busybox
90e01955edcd: Already exists
Digest: sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812
Status: Downloaded newer image for busybox:1.29
docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "hello world": executable file not found in $PATH": unknown.
ERRO[0004] error waiting for container: context canceled
λ bgarcial [~] → sudo docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
busybox 1.29 59788edf1f3e 2 months ago 1.15MB
hello-world latest 4ab4c602aa5e 3 months ago 1.84kB
λ bgarcial [~] →
With other images don't happen the same error, like the command sudo docker run mongo:4-xenial
...
Is possible that my problem could be when I pass the "hello world" as an argument to execute into my container?
docker
add a comment |
up vote
0
down vote
favorite
I want to download the busybox image and I get it but despite it I have the following error:
λ bgarcial [~] → sudo docker run busybox:1.29 "hello world"
Unable to find image 'busybox:1.29' locally
1.29: Pulling from library/busybox
90e01955edcd: Already exists
Digest: sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812
Status: Downloaded newer image for busybox:1.29
docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "hello world": executable file not found in $PATH": unknown.
ERRO[0004] error waiting for container: context canceled
λ bgarcial [~] → sudo docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
busybox 1.29 59788edf1f3e 2 months ago 1.15MB
hello-world latest 4ab4c602aa5e 3 months ago 1.84kB
λ bgarcial [~] →
With other images don't happen the same error, like the command sudo docker run mongo:4-xenial
...
Is possible that my problem could be when I pass the "hello world" as an argument to execute into my container?
docker
2
You should useecho "hello world"
; what you passed isn't a valid shell command so the container didn't know how to run it, same as if you typed it on a command line.
– Stephen Harris
Dec 8 at 4:01
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want to download the busybox image and I get it but despite it I have the following error:
λ bgarcial [~] → sudo docker run busybox:1.29 "hello world"
Unable to find image 'busybox:1.29' locally
1.29: Pulling from library/busybox
90e01955edcd: Already exists
Digest: sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812
Status: Downloaded newer image for busybox:1.29
docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "hello world": executable file not found in $PATH": unknown.
ERRO[0004] error waiting for container: context canceled
λ bgarcial [~] → sudo docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
busybox 1.29 59788edf1f3e 2 months ago 1.15MB
hello-world latest 4ab4c602aa5e 3 months ago 1.84kB
λ bgarcial [~] →
With other images don't happen the same error, like the command sudo docker run mongo:4-xenial
...
Is possible that my problem could be when I pass the "hello world" as an argument to execute into my container?
docker
I want to download the busybox image and I get it but despite it I have the following error:
λ bgarcial [~] → sudo docker run busybox:1.29 "hello world"
Unable to find image 'busybox:1.29' locally
1.29: Pulling from library/busybox
90e01955edcd: Already exists
Digest: sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812
Status: Downloaded newer image for busybox:1.29
docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "hello world": executable file not found in $PATH": unknown.
ERRO[0004] error waiting for container: context canceled
λ bgarcial [~] → sudo docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
busybox 1.29 59788edf1f3e 2 months ago 1.15MB
hello-world latest 4ab4c602aa5e 3 months ago 1.84kB
λ bgarcial [~] →
With other images don't happen the same error, like the command sudo docker run mongo:4-xenial
...
Is possible that my problem could be when I pass the "hello world" as an argument to execute into my container?
docker
docker
asked Dec 8 at 3:40
bgarcial
1033
1033
2
You should useecho "hello world"
; what you passed isn't a valid shell command so the container didn't know how to run it, same as if you typed it on a command line.
– Stephen Harris
Dec 8 at 4:01
add a comment |
2
You should useecho "hello world"
; what you passed isn't a valid shell command so the container didn't know how to run it, same as if you typed it on a command line.
– Stephen Harris
Dec 8 at 4:01
2
2
You should use
echo "hello world"
; what you passed isn't a valid shell command so the container didn't know how to run it, same as if you typed it on a command line.– Stephen Harris
Dec 8 at 4:01
You should use
echo "hello world"
; what you passed isn't a valid shell command so the container didn't know how to run it, same as if you typed it on a command line.– Stephen Harris
Dec 8 at 4:01
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
When you pass a command to the Docker container, it has to be executable from the shell inside the Docker container. In this case, 'Hello World' is treated as the name of the executable you are trying to run. Since this is not a valid executable name, Docker returns the following error.
[root@testvm1 test]# docker run busybox "Hello World"
container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH"
/usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH".
Note the line: "exec: "Hello World": executable file not found in $PATH"
.
Use a command valid inside the container, such as echo
for this to work:
[root@testvm1 test]# docker run busybox echo "Hello World"
Hello World
Note that you will see the same behaviour if you run the container interactively by using a shell:
[root@testvm1 test]# docker run -it busybox /bin/sh
/ # "Hello World"
/bin/sh: Hello World: not found
/ # echo "Hello World"
Hello World
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f486713%2fdownloaded-newer-image-docker-error-response-from-daemon-oci-runtime-create%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
When you pass a command to the Docker container, it has to be executable from the shell inside the Docker container. In this case, 'Hello World' is treated as the name of the executable you are trying to run. Since this is not a valid executable name, Docker returns the following error.
[root@testvm1 test]# docker run busybox "Hello World"
container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH"
/usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH".
Note the line: "exec: "Hello World": executable file not found in $PATH"
.
Use a command valid inside the container, such as echo
for this to work:
[root@testvm1 test]# docker run busybox echo "Hello World"
Hello World
Note that you will see the same behaviour if you run the container interactively by using a shell:
[root@testvm1 test]# docker run -it busybox /bin/sh
/ # "Hello World"
/bin/sh: Hello World: not found
/ # echo "Hello World"
Hello World
add a comment |
up vote
2
down vote
accepted
When you pass a command to the Docker container, it has to be executable from the shell inside the Docker container. In this case, 'Hello World' is treated as the name of the executable you are trying to run. Since this is not a valid executable name, Docker returns the following error.
[root@testvm1 test]# docker run busybox "Hello World"
container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH"
/usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH".
Note the line: "exec: "Hello World": executable file not found in $PATH"
.
Use a command valid inside the container, such as echo
for this to work:
[root@testvm1 test]# docker run busybox echo "Hello World"
Hello World
Note that you will see the same behaviour if you run the container interactively by using a shell:
[root@testvm1 test]# docker run -it busybox /bin/sh
/ # "Hello World"
/bin/sh: Hello World: not found
/ # echo "Hello World"
Hello World
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
When you pass a command to the Docker container, it has to be executable from the shell inside the Docker container. In this case, 'Hello World' is treated as the name of the executable you are trying to run. Since this is not a valid executable name, Docker returns the following error.
[root@testvm1 test]# docker run busybox "Hello World"
container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH"
/usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH".
Note the line: "exec: "Hello World": executable file not found in $PATH"
.
Use a command valid inside the container, such as echo
for this to work:
[root@testvm1 test]# docker run busybox echo "Hello World"
Hello World
Note that you will see the same behaviour if you run the container interactively by using a shell:
[root@testvm1 test]# docker run -it busybox /bin/sh
/ # "Hello World"
/bin/sh: Hello World: not found
/ # echo "Hello World"
Hello World
When you pass a command to the Docker container, it has to be executable from the shell inside the Docker container. In this case, 'Hello World' is treated as the name of the executable you are trying to run. Since this is not a valid executable name, Docker returns the following error.
[root@testvm1 test]# docker run busybox "Hello World"
container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH"
/usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: "Hello World": executable file not found in $PATH".
Note the line: "exec: "Hello World": executable file not found in $PATH"
.
Use a command valid inside the container, such as echo
for this to work:
[root@testvm1 test]# docker run busybox echo "Hello World"
Hello World
Note that you will see the same behaviour if you run the container interactively by using a shell:
[root@testvm1 test]# docker run -it busybox /bin/sh
/ # "Hello World"
/bin/sh: Hello World: not found
/ # echo "Hello World"
Hello World
answered Dec 8 at 6:12
Haxiel
921310
921310
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f486713%2fdownloaded-newer-image-docker-error-response-from-daemon-oci-runtime-create%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
2
You should use
echo "hello world"
; what you passed isn't a valid shell command so the container didn't know how to run it, same as if you typed it on a command line.– Stephen Harris
Dec 8 at 4:01