search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.84k stars 282 forks source link

OCI runtime exec failed: exec failed: unable to start container process: error writing config to pipe: write init-p: broken pipe: unknown #13237

Open cforce opened 1 year ago

cforce commented 1 year ago
  1. Docker build following file https://github.com/spring-cloud/spring-cloud-function/blob/main/spring-cloud-function-samples/function-sample-aws-native/Dockerfile
  2. Shall work without issues, as its the case for standard linux env.
  3. On Docker4Desktop it fails with below message. 
    
Successfully built 7c4e0f348c25
Build completed

Launching introspection container� Done, container launched: aca1ff8ad374 Introspecting image environment variables� Done, 23 variables found in the inspect results Introspecting $JAVA_HOME: /usr/lib/graalvm

java -version

OCI runtime exec failed: exec failed: unable to start container process: error writing config to pipe: write init-p: broken pipe: unknown

Introspection completed with error: java.util.NoSuchElementException: No element of the collection was transformed to a non-null value. Removing introspection container

radub commented 1 year ago

I have the same issue with a Laravel application on Docker Mac OS. @cforce were you able to track down the root cause?

cforce commented 1 year ago

nope.