During a balena cloud build I see this log:
zstack-zigbee-reader] Step 3/11 : RUN apk add --no-cache g++ linux-headers make python
[zstack-zigbee-reader] ---> Running in d60f783d8567
[zstack-zigbee-reader] standard_init_linux.go:207: exec user process caused "no such file or directory"
[zstack-zigbee-reader] Removing intermediate container d60f783d8567
[zstack-zigbee-reader] The command '/bin/sh -c apk add --no-cache g++ linux-headers make python' returned a non-zero code: 1
The build is triggered via git push.
The Dockerfile.template:
FROM balenalib/%%BALENA_ARCH%%-alpine-node:12-latest-build as build
WORKDIR /app
RUN apk add --no-cache \
# node-gyp, required by zigbee-herdsman
g++ \
linux-headers \
make \
python
The app architecture is aarch64.
On April 20, the build was ok.
On April 27, the build was broken (Dockerfile and other configuration files unchanged).
What might have changed:
- The docker base image (I use the
-latest-buildtag). - Something in the balena cloud build infrastructure, perhaps related to ARM emulation?
- Similar old topic: Resolve "The command '/bin/sh -c apk update && apk add jq' returned a non-zero code: 1". There the problem occurred during a local build. My problem is during the cloud build.