The Error “OCI runtime exec failed: exec failed: unable to start container process:”, is an error that is invoked when you are working on a docker app and are trying to use the web bash command.
Given below is the snippet of the error you might get:
OCI runtime exec failed: exec failed: unable to start container process:The error “OCI runtime exec failed: exec failed: unable to start container process:” might be seen because of a runc component upstream problem, this could occur on a kernel with selinux enabled.
To fix the error, “OCI runtime exec failed: exec failed: unable to start container process:” you will have to use the setsebool workaround using command ‘setsebool -P daemons_dump_core on’. You can also try to restart your docker to fix the issue.
First, you will have to use the setsebool workaround to fix the issue.
To use this workaround you will have to use the code mentioned below along with the correct policy:
setsebool -P daemons_dump_core onYou will have to use the policy mentioned below to fix the error:
module mydocker 1.0;
require {
type container_runtime_t;
type init_t;
class bpf prog_run;
}If the above code and policy do not work for you and you are still facing the same error, then you will have to restart your docker and the operating system you are using.
This should help you fix the error, “OCI runtime exec failed: exec failed: unable to start container process:”
Conclusion
To fix the error, “OCI runtime exec failed: exec failed: unable to start container process:” you will have to use the setsebool workaround to fix the issue.
You can also try to restart your docker to fix the issue. This is because because of a runc component upstream problem, this could occur on a kernel with selinux enabled.