build.sh: not found

[x-dean]

Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
[1/2] STEP 1/13: FROM golang:1.17-alpine AS build
[1/2] STEP 2/13: RUN apk update && apk upgrade && apk add --no-cache git nodejs bash npm
--> Using cache 9c197f4e791a9958d4cb7f766ce967e151beabad49d3bb149242172e6306a133
--> 9c197f4e791
[1/2] STEP 3/13: RUN go get -u github.com/jteeuwen/go-bindata/...
--> Using cache 2c19a9860e80b2505adb1d49e944e30cafa0bb364a3458b625cce90daf62ce73
--> 2c19a9860e8
[1/2] STEP 4/13: RUN go get github.com/tools/godep
--> Using cache 33b8137d6f393cfeec2e40a677094bc9d42536ba07c09667294be62ff325b65a
--> 33b8137d6f3
[1/2] STEP 5/13: RUN go get github.com/kubernetes-up-and-running/kuard
--> Using cache ed77655f1a9c4e4fa6aa30fc69dbf14d0f7785bba4460b499c56dbaf7497b073
--> ed77655f1a9
[1/2] STEP 6/13: WORKDIR /go/src/github.com/kubernetes-up-and-running/kuard
--> Using cache a77ee93c189674aca28e0b6e8f4fe0c9c87882e16995d2d8a809fae33e7c8dc5
--> a77ee93c189
[1/2] STEP 7/13: COPY . .
--> Using cache c70ff6f35a3a6a34acbd9838fc2b9250c155078ea7924d3346a83b497b9ec4a9
--> c70ff6f35a3
[1/2] STEP 8/13: ENV VERBOSE=0
--> Using cache 5246faebb47be5deb520fed5ad960858816a5be096c93632b096c4e4eb32dd3d
--> 5246faebb47
[1/2] STEP 9/13: ENV PKG=github.com/kubernetes-up-and-running/kuard
--> Using cache 1082633b1420cb6d147428b68d26d888e2a23b68cd9d8007b74569dad9a4d1c6
--> 1082633b142
[1/2] STEP 10/13: ENV ARCH=amd64
--> Using cache 280e5b84381a02a4194526f8afbbce68428775dea04a25542ad89f870843144e
--> 280e5b84381
[1/2] STEP 11/13: ENV VERSION=test
--> Using cache 9fce4dd8d57726f9184523397a1782317a8c02c84684f199d28612182fd2633a
--> 9fce4dd8d57
[1/2] STEP 12/13: RUN build/build.sh
/bin/sh: build/build.sh: not found
Error: error building at STEP "RUN build/build.sh": error while running runtime: exit status 127

[lachie83]

Hi @x-dean, did you checkout the repository and run the container build command from the root directory of the repository? From the output you provided, build/build.sh cannot be found from the context directory you provided to the container build command.

[cristisulighetean]

The issue has been solved in the last post of #30