docker executes the command:docker exec -it 1e33b26152e1 /bin/bash
Error on entering container: OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caused “exec: \”/bin/bash\”: stat /bin/bash: no such file or directory”: unknown
Error scenario:I am pulling a registry image to build a private repository. I ran the registry image and then entered the container.
Error on entering container: OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caused “exec: \”/bin/bash\”: stat /bin/bash: no such file or directory”: unknown
Error scenario:I am pulling a registry image to build a private repository. I ran the registry image and then entered the container.
Solution:
docker exec -it 1e33b26152e1 /bin/sh
or
docker exec -it 1e33b26152e1 bash
or
docker exec -it 1e33b26152e1 sh
docker exec -it 1e33b26152e1 /bin/sh
or
docker exec -it 1e33b26152e1 bash
or
docker exec -it 1e33b26152e1 sh
Similar Posts:
- [Solved] 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
- [Solved] OCI runtime exec failed……executable file not found in $PATH”: unknown
- Solutions to docker pull error reporting
- The docker container reports an error when using the systemctl command
- [Solved] http: server gave HTTP response to HTTPS client
- Docker startup container Error response from daemon: OCI runtime create failed: container_ linux.go:349
- docker: Error response from daemon: Conflict. The container name “/xx” is already in use
- [Solved] Docker Starup Error: Failed to start Docker Application Container Engine.
- failed: OCI runtime create failed: container_linux.go:348
- Failed to get D-Bus connection: Operation not permitted [docker Install centos7]