Docker Container Error

The following type of error can occur when adding a secondary service container for your job:

Unexpected 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

This usually occurs due to a bad command being passed to one of the secondary service containers in your job. 

The error message occurs due to the secondary service container crashing or exiting prematurely. This means CircleCI cannot get the PID from the Docker daemon and exits with a failure.

Ensure that the command and/or entrypoint are correct so that the container can spin up successfully. This can be be tested locally by using the CircleCI CLI to run the job locally and ensure Docker spins up all containers successfully. To resolve the error, check out the documentation for the docker image defined in your config to see which commands can be used at spin up.

Additional Resources

• Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: “python”: