Background
When the compiled image is exported and loaded into another computer, the error is as follows:
//import mirror
docker import example.tar
//run the docker
docker run -it example:v20210119 /bin/bash
//error:
docker: 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.
For the description of this problem, there are probably two kinds of factional explanations on the Internet under Google
Left wing school
There is no/bin/bash in production, try/bin/sh, the result is still the problem
Right wing
Compatibility between Linux and docker. Then uninstall the old version and install the latest one.
The solution of the left faction is very easy to verify. After repeated verification, the problem is still unsolved. It is commonly known as the left faction.
The solution of the right faction is a bit difficult to verify, but intuition tells me that it should not be such a problem
Sure enough, I saw the right answer. After a careful look, a short description and a quick verification, the problem was solved.
this error occurs when docker runs. It is caused by different ways of saving the image. If the image is imported by using import, it should be noted that import can import the image package saved by save and the container package saved by export. However, if the image package saved by save is imported, there is no error. But this error occurs when run runs
-
- solutions
docker load < buildroot_v20210119.tar
Read More:
- [Solved] docker Error response from daemon OCI runtime create failed container_linux.go380
- [Solved] Error response from daemon: OCI runtime create failed: container with id exists: xxzxxxxxxxx
- Docker Create or Start Nginx Error: docker: Error response from daemon: driver failed programming external connectivity
- Docker Error response from daemon: Get https://registry-1.docker.io/v2/: x509: certificate has expired or is not yet valid
- Docker Error response from daemon: Get https://registry-1.docker.io/v2/portainer/portainer/…
- [Solved] Docker: Error response from daemon: driver failed programming external connectivity on endpoint mysq
- [Solved] docker: Error response from daemon: driver failed programming external connectivity on endpoint mysql-test …
- [Solved] Docker Error: Error response from daemon: driver failed programming external connectivity on endpoint
- Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen is reported when docker port mapping or starting the container
- Mac Docker pull Error: Error response from daemon: Get https://xx.xx.xx.xx/v2/: Service Unavailable
- [Solved] Docker Error: got permission denied while trying to connect to the docker daemon socket at…
- How to Fix ERROR Couldn’t connect to Docker daemon at http+docker://localunixsocket
- Docker Open Error: Warning: docker.service changed on disk. Run ‘systemctl daemon-reload‘ to reload unit
- [Solved] Error response from daemon: Get “*“: x509: certificate signed by unknown authority
- [Solved] Docker failed to start daemon: error initializing graphdriver: driver not supported
- [Solved] error during connect: This error may indicate that the docker daemon is not running
- [Solved] Docker Startup Error: panic: runtime error: invalid memory address or nil pointer dereference
- [Solved] CentOS build a docker error: job for docker.service failed….
- [Solved] docker Error: bridge docker0 failed: exchange full
- How to Solve Error: could not read ok from ADB Server.failed to start daemon error: cannot connect to daemon