OCI runtime exec failed: container_linux.go:344: starting container process caused “no such file or directory”: unknown

问题

I'm running sample tutorial from https://hyperledger-fabric.readthedocs.io/en/release-1.4.html, trying to run the "Build Your First Network" ./byfn.sh. Network generation works fine, but when I try to up the network, i receive the following error:

$cd..../fabric-samples/first-network
$./byfn.sh generate
$./byfn.sh up

    Starting for channel 'mychannel' with CLI timeout of '10' seconds and 
    CLI delay of '3' seconds
    Continue? [Y/n] y
    proceeding ...
    LOCAL_VERSION=1.4.1
    DOCKER_IMAGE_VERSION=1.4.1
    Creating peer0.org1.example.com ... done
    Creating peer1.org2.example.com ... done
    Creating peer0.org2.example.com ... done
    Creating orderer.example.com    ... done
    Creating peer1.org1.example.com ... done
    Creating cli                    ... done

    **OCI runtime exec failed: exec failed: container_linux.go:344: starting 
    container process caused "no such file or directory": unknown
    ERROR !!!! Test failed**

回答1:

Reinstalled docker, deleted previous node modules, re-run the network, finally worked fine.

$./byfn.sh down
$docker rm $(docker ps -a -q)
$docker volume prune
$./byfn.sh generate
$./byfn.sh up

回答2:

If you take the workaround using sh:

Using the docker command docker exec -it <your container> sh will allow you to overcome the issue. It does appear that bash is not installed in the container.

Source: OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: "bash": executable file not found in $PATH": unknown

来源：https://stackoverflow.com/questions/56489157/oci-runtime-exec-failed-container-linux-go344-starting-container-process-caus

标签

hyperledger-fabric