CODEWITHSUNDEEP
azuredockerazure-iot-hubazure-iot-edgeazure-container-registry
iAmoric
iAmoric

Reputation: 1967

Azure IoT Edge Module : Error while Build and Push IoT Edge Solution

I followed this tutorial step by step : https://learn.microsoft.com/en-us/azure/iot-edge/tutorial-c-module

But at the step "Build and Push your solution" (https://learn.microsoft.com/en-us/azure/iot-edge/tutorial-c-module#build-and-push-your-solution) I have the following error in the terminal : 

standard_init_linux.go:207: exec user process caused "no such file or directory"

I check the 3 points listed on the tutorials ("If you receive an error trying to build and push your module") but I still have the error.

I don't even know what file it is about..

Do someone have an idea of the problem ?

Thanks

EDIT

I add all the terminal output : 

Sending build context to Docker daemon    106kB
Step 1/14 : FROM arm32v7/ubuntu:xenial AS base
 ---> 8593318db04f
Step 2/14 : RUN apt-get update && apt-get install -y --no-install-recommends software-properties-common && add-apt-repository -y ppa:aziotsdklinux/ppa-azureiot && apt-get update && apt-get install -y azure-iot-sdk-c-dev && rm -rf /var/lib/apt/lists/*
 ---> Running in 8bed4f396527
standard_init_linux.go:207: exec user process caused "no such file or directory"
The command '/bin/sh -c apt-get update && apt-get install -y --no-install-recommends software-properties-common && add-apt-repository -y ppa:aziotsdklinux/ppa-azureiot && apt-get update && apt-get install -y azure-iot-sdk-c-dev && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 1

Upvotes: 2

Views: 707

Answers (2)

Wei
Wei

Reputation: 51

It seems you are building arm32v7 image, so what os is your host machine? Can you try to build the amd64 image instead of arm32v7?

Upvotes: 0

Christian Waters
Christian Waters

Reputation: 91

Looks like one of the paths in your command cannot be found in the intermediate docker image. Try running a shell directly on the intermediate image using:

docker run -it --entrypoint sh 8593318db04f

to check /var/lib/apt/lists/ and /bin/sh are actually present on the image. You should be able to manually run the command specified in your docker file.

I have found that quite helpful in debugging failing docker builds.

Upvotes: 2

Related Questions