An error was reported when using docker to enter the specified container today. The screenshot of the error is as follows:
After careful verification, the command is correct, but it can’t get into the container. After checking the data, it is realized that there is a problem with the docker. It can be understood in combination with the error report:
Error response from daemon: OCI runtime exec failed: exec failed: container_linux.go:345: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown
The above is complete error reporting information, of which the key information is as follows:
"/bin/bash\": stat /bin/bash: no such file or directory": unknown
That is, there is no directory/bin/bash, so an error will be reported when you want to enter the container according to the initial command.
You can enter by using the following command. The screenshot is as follows:
docker exec -it mqtt /bin/sh
Perfect solution, record notes!
Read More:
- Error response from daemon: OCI runtime create failed: container_linux.go:380
- The docker runtime container reported an error: error response from daemon: OCI runtime create failed
- Docke Run: response from daemon: OCI runtime create failed: container with id exists:XXX:unknown
- Docker run failed with the following error in logs, standard_ init_ linux.go:211 : exec user process caused “exec format error“
- standard_init_linux.go:211: exec user process caused “exec format error”
- Error running docker container: starting container process caused “exec: \“python\“: executable file
- Fedora32 start container error – OCI runtime create failed: This version of runc doesn’t work on cgroups V2: unknown
- Failed to execute goal org.codehaus.mojo:exec-maven-plugin:3.0.0:exec (default-cli) on project Hello
- standard_init_linux.go:178: exec user process caused “no such file or directory”
- Common linux commands — find command’s Exec
- When docker creates a container command: Error response from daemon: No command specified
- Solve cannot execute binary file: exec format error under Linux
- Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0
- insmod: init_module ‘hello.ko’ failed (Exec format error)
- Docker creation container cannot find network card: error response from daemon: network XXXX not found
- docker: Error response from daemon: driver failed programming external connectivity on endpoint
- Failed: execution error, return code 1 from org.apache.hadoop . hive.ql.exec .DDLTask…
- Rsync: failed to exec SSH: no such error in remote Rsync
- FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(me
- docker: Error response from daemon: driver failed programming external connectivity on endpoint lamp