Breaking News: Grepper is joining You.com. Read the official announcement!

oci runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

Ziyad taleb answered on June 10, 2022 Popularity 3/10 Helpfulness 1/10

answer oci runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

oci runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

Comment

This error message typically indicates that the /bin/bash binary is not present inside the container,
or it is not installed in the container's base image.

To resolve this issue, you can try using a different shell binary that is available inside the container,
such as /bin/sh. Alternatively, you can try installing the bash package inside the container using the package manager that is available in the container's operating system.

If you are using a container image that you did not create yourself, 
it is possible that the image does not include the required binary or package. 
In this case, you may need to use a different container image that includes the necessary components,
or create your own custom image that includes them.

Popularity 3/10 Helpfulness 1/10 Language whatever

Source: Grepper

Tags: exec file process runtime stat whatever

Link to this answer
Share Copy Link

Contributed on Feb 13 2023

Ziyad taleb

0 Answers Avg Quality 2/10

Closely Related Answers

OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

Comment

use /bin/sh instead of /bin/bash

Popularity 9/10 Helpfulness 5/10 Language whatever

Source: Grepper

Tags: exec file

Link to this answer
Share Copy Link

Contributed on Jun 10 2022

Expensive Earthworm

0 Answers Avg Quality 2/10

oci runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

Contents

More Related Answers

oci runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

Closely Related Answers

OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.