Are you struggling with the Docker OCI runtime create failed error message? Our Docker Support team is here to lend a hand with your queries and issues.

OCI runtime create failed error: Resolved

The OCI runtime create failed error message often occurs in Docker when a bad command is passed to one of the secondary service containers in the job.

Docker OCI runtime create failedUnexpected environment preparation error: Error response from daemon:
OCI runtime create failed: container_linux.go:345:
starting container process caused “process_linux.go:303:
getting the final child’s pid from pipe caused \”EOF\””: unknown

In other words, the error occurs as a result of the secondary service container exiting prematurely or crashing. As a result, the CircleCI is not able to access the PID from the Docker daemon and ultimately exits.

Fortunately, there is an easy fix for this issue. All we have to do is make sure that the command and the entrypoint directives are accurate so that the container is able to spin up successfully.

We can test this locally via the CircleCI CLI and run the job locally. Here, we will be checking if Docker spins up all containers successfully. In case not, we have to refer to the documentation for the docker image defined in the config to verify which commands have to be utilized at spin up.

If this does not work, try restarting the Docker service. Alternatively, we can perform a docker disk image reset to resolve the error.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

To conclude, our Support Engineers demonstrated the cause behind the OCI runtime create failed error and how to resolve it easily.