Docker function - error response OCI runtime create failed
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I'm working with the book Docker in action and I'm trying to work with Docker.
When I run the following commands:
docker run --name export-test
dockerinaction/ch7_packed:latest ./echo For Export
docker export --output contents.tar export-test
docker rm export-test
tar -tf contents.tar
the console returns me:
I get the following error message:
Error response from daemon: OCI runtime create failed:
container_linux.go:348: starting container process caused "exec:
"/bin/bash": stat /bin/bash: no such file or directory": unknown.
I tried to find a solution, but could not find one that works. I have rebooted Docker and it is still doesn't works!
docker
edited Sep 15 at 14:59
Rui F Ribeiro
36.8k1273117
asked Sep 13 at 19:26
Webman
1577
add a comment |Â
up vote
3
down vote
favorite
I'm working with the book Docker in action and I'm trying to work with Docker.
When I run the following commands:
docker run --name export-test
dockerinaction/ch7_packed:latest ./echo For Export
docker export --output contents.tar export-test
docker rm export-test
tar -tf contents.tar
the console returns me:
I get the following error message:
Error response from daemon: OCI runtime create failed:
container_linux.go:348: starting container process caused "exec:
"/bin/bash": stat /bin/bash: no such file or directory": unknown.
I tried to find a solution, but could not find one that works. I have rebooted Docker and it is still doesn't works!
docker
edited Sep 15 at 14:59
Rui F Ribeiro
36.8k1273117
asked Sep 13 at 19:26
Webman
1577
seems to be a common issue. Please see below.
– Goro
Sep 14 at 12:09
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm working with the book Docker in action and I'm trying to work with Docker.
When I run the following commands:
docker run --name export-test
dockerinaction/ch7_packed:latest ./echo For Export
docker export --output contents.tar export-test
docker rm export-test
tar -tf contents.tar
the console returns me:
I get the following error message:
Error response from daemon: OCI runtime create failed:
container_linux.go:348: starting container process caused "exec:
"/bin/bash": stat /bin/bash: no such file or directory": unknown.
I tried to find a solution, but could not find one that works. I have rebooted Docker and it is still doesn't works!
docker
edited Sep 15 at 14:59
Rui F Ribeiro
36.8k1273117
asked Sep 13 at 19:26
Webman
1577
I'm working with the book Docker in action and I'm trying to work with Docker.
When I run the following commands:
docker run --name export-test
dockerinaction/ch7_packed:latest ./echo For Export
docker export --output contents.tar export-test
docker rm export-test
tar -tf contents.tar
the console returns me:
I get the following error message:
Error response from daemon: OCI runtime create failed:
container_linux.go:348: starting container process caused "exec:
"/bin/bash": stat /bin/bash: no such file or directory": unknown.
I tried to find a solution, but could not find one that works. I have rebooted Docker and it is still doesn't works!
docker
docker
edited Sep 15 at 14:59
Rui F Ribeiro
36.8k1273117
asked Sep 13 at 19:26
Webman
1577
edited Sep 15 at 14:59
Rui F Ribeiro
36.8k1273117
asked Sep 13 at 19:26
Webman
1577
edited Sep 15 at 14:59
Rui F Ribeiro
36.8k1273117
edited Sep 15 at 14:59
Rui F Ribeiro
36.8k1273117
edited Sep 15 at 14:59
Rui F Ribeiro
36.8k1273117
36.8k1273117
asked Sep 13 at 19:26
Webman
1577
asked Sep 13 at 19:26
Webman
1577
asked Sep 13 at 19:26
Webman
1577
1577
seems to be a common issue. Please see below.
– Goro
Sep 14 at 12:09
add a comment |Â
seems to be a common issue. Please see below.
– Goro
Sep 14 at 12:09
seems to be a common issue. Please see below.
– Goro
Sep 14 at 12:09
seems to be a common issue. Please see below.
– Goro
Sep 14 at 12:09
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
4
down vote
Probably you are running an old version of Linux, or it is just a compatibility issue. Also, this error may indicate an issue with the docker daemon itself, not the container you are trying to run. Try to delete all containers, and restart the daemon. Also try to clean up the docker networks.
Please see here detailed explanation about the problem, and here are the OS requirements for the Docker to work properly. In addition, you can find more information here
answered Sep 14 at 11:44
Goro
5,47052460
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
Probably you are running an old version of Linux, or it is just a compatibility issue. Also, this error may indicate an issue with the docker daemon itself, not the container you are trying to run. Try to delete all containers, and restart the daemon. Also try to clean up the docker networks.
Please see here detailed explanation about the problem, and here are the OS requirements for the Docker to work properly. In addition, you can find more information here
answered Sep 14 at 11:44
Goro
5,47052460
add a comment |Â
up vote
4
down vote
Probably you are running an old version of Linux, or it is just a compatibility issue. Also, this error may indicate an issue with the docker daemon itself, not the container you are trying to run. Try to delete all containers, and restart the daemon. Also try to clean up the docker networks.
Please see here detailed explanation about the problem, and here are the OS requirements for the Docker to work properly. In addition, you can find more information here
answered Sep 14 at 11:44
Goro
5,47052460
add a comment |Â
up vote
4
down vote
up vote
4
down vote
Probably you are running an old version of Linux, or it is just a compatibility issue. Also, this error may indicate an issue with the docker daemon itself, not the container you are trying to run. Try to delete all containers, and restart the daemon. Also try to clean up the docker networks.
Please see here detailed explanation about the problem, and here are the OS requirements for the Docker to work properly. In addition, you can find more information here
answered Sep 14 at 11:44
Goro
5,47052460
Probably you are running an old version of Linux, or it is just a compatibility issue. Also, this error may indicate an issue with the docker daemon itself, not the container you are trying to run. Try to delete all containers, and restart the daemon. Also try to clean up the docker networks.
Please see here detailed explanation about the problem, and here are the OS requirements for the Docker to work properly. In addition, you can find more information here
answered Sep 14 at 11:44
Goro
5,47052460
edited Sep 14 at 11:49
answered Sep 14 at 11:44
Goro
5,47052460
answered Sep 14 at 11:44
Goro
5,47052460
answered Sep 14 at 11:44
Goro
5,47052460
5,47052460
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f468877%2fdocker-function-error-response-oci-runtime-create-failed%23new-answer', 'question_page');
);
Post as a guest
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
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
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
seems to be a common issue. Please see below.
– Goro
Sep 14 at 12:09