Closed AL1041713 closed 1 year ago
OmidTahouri
commented
1 year ago I just ran the same command in Cloud Shell and successfully built a new image (Docker version 20.10.21). Is this a reproducable issue or did you only attempt it once?
Please could you also check your Docker version.
AL1041713
commented
1 year ago I got the same as you do, from Cloud Shell it is working fine, I don't understand what is the difference.
It's totally reproducable, Locally I tried to start from zero, cloning a fresh devrel repo and tried directly to run the cmd ./build.sh -t apigee-sackmesser Running on Mac computer with M1 Pro - Docker version 20.10.20, build 9fdeb9c
I got this
valentinmalard@HEL-DF-JW2X7KVWNM apigee-sackmesser % ./build.sh -t apigee-sackmesser
[+] Building 23.2s (7/14)
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 37B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 34B 0.0s
=> [internal] load metadata for docker.io/library/maven:3.6-alpine 0.4s
=> [ 1/10] FROM docker.io/library/maven:3.6-alpine@sha256:16691dc7e18e5311ee7ae38b40dcf98ee1cfe4a487fdd0e57bfef76a0415034a 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 8.49kB 0.0s
=> CACHED [ 2/10] RUN apk add --no-cache git jq libxml2-utils nodejs npm unzip 0.0s
=> ERROR [ 3/10] RUN npm install --global apigeelint@2.10.0 22.7s
------
> [ 3/10] RUN npm install --global apigeelint@2.10.0:
#6 2.937 npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
#6 14.33 npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
#6 17.36 npm WARN deprecated har-validator@5.1.5: this library is no longer supported
#6 17.51 npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
#6 22.12 /usr/bin/apigeelint -> /usr/lib/node_modules/apigeelint/cli.js
#6 22.16
#6 22.16 > es5-ext@0.10.62 postinstall /usr/lib/node_modules/apigeelint/node_modules/es5-ext
#6 22.16 > node -e "try{require('./_postinstall')}catch(e){}" || exit 0
#6 22.16
#6 22.56 npm WARN notsup Unsupported engine for chalk@5.2.0: wanted: {"node":"^12.17.0 || ^14.13 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.13.4"})
#6 22.56 npm WARN notsup Not compatible with your version of node/npm: chalk@5.2.0
#6 22.56 npm WARN notsup Unsupported engine for eslint@8.30.0: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.13.4"})
#6 22.56 npm WARN notsup Not compatible with your version of node/npm: eslint@8.30.0
#6 22.56 npm WARN notsup Unsupported engine for pdfmake@0.2.7: wanted: {"node":">=12"} (current: {"node":"10.19.0","npm":"6.13.4"})
#6 22.56 npm WARN notsup Not compatible with your version of node/npm: pdfmake@0.2.7
#6 22.56 npm WARN notsup Unsupported engine for eslint-scope@7.1.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.13.4"})
#6 22.56 npm WARN notsup Not compatible with your version of node/npm: eslint-scope@7.1.1
#6 22.56 npm WARN notsup Unsupported engine for @humanwhocodes/module-importer@1.0.1: wanted: {"node":">=12.22"} (current: {"node":"10.19.0","npm":"6.13.4"})
#6 22.56 npm WARN notsup Not compatible with your version of node/npm: @humanwhocodes/module-importer@1.0.1
#6 22.56 npm WARN notsup Unsupported engine for eslint-visitor-keys@3.3.0: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.13.4"})
#6 22.56 npm WARN notsup Not compatible with your version of node/npm: eslint-visitor-keys@3.3.0
#6 22.56 npm WARN notsup Unsupported engine for @eslint/eslintrc@1.4.0: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.13.4"})
#6 22.56 npm WARN notsup Not compatible with your version of node/npm: @eslint/eslintrc@1.4.0
#6 22.56 npm WARN notsup Unsupported engine for espree@9.4.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.13.4"})
#6 22.56 npm WARN notsup Not compatible with your version of node/npm: espree@9.4.1
#6 22.56
#6 22.57 npm ERR! Maximum call stack size exceeded
#6 22.58
#6 22.58 npm ERR! A complete log of this run can be found in:
#6 22.58 npm ERR! /root/.npm/_logs/2022-12-20T10_03_29_598Z-debug.logAnd it's also reproducable on Github Workflow running on : Docker version 20.10.21+azure-2, build baeda1f82a10204ec5708d5fbba130ad76cfee49
danistrebel
commented
1 year ago Hi @AL1041713, I thanks for the report. I am not able to reporduce it on my end but I bumped the Dockerfile with the latest versions to get rid of the npm issues.
I'd be curious if the Dockerfile in here https://github.com/apigee/devrel/pull/633/files would solve your issue that you see. If you're willing to try this locally with the updated Dockerfile, please let us know if it changes anything.
AL1041713
commented
1 year ago Yes it is 🥇 once pulled the new repo version it worked locally valentinmalard@HEL-DF-JW2X7KVWNM apigee-sackmesser % ./build.sh -t apigee-sackmesser
[+] Building 28.5s (14/14) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 1.31kB 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 34B 0.0s
=> [internal] load metadata for docker.io/library/alpine:3.17 2.2s
=> [1/9] FROM docker.io/library/alpine:3.17@sha256:8914eb54f968791faf6a8638949e480fef81e697984fba772b3976835194c6d4 0.4s
=> => resolve docker.io/library/alpine:3.17@sha256:8914eb54f968791faf6a8638949e480fef81e697984fba772b3976835194c6d4 0.0s
=> => sha256:8914eb54f968791faf6a8638949e480fef81e697984fba772b3976835194c6d4 1.64kB / 1.64kB 0.0s
=> => sha256:af06af3514c44a964d3b905b498cf6493db8f1cde7c10e078213a89c87308ba0 528B / 528B 0.0s
=> => sha256:d3156fec8bcbc7b491a4edc271a7734dcfa186fc73282d4e120eeaaf2ce95c43 1.49kB / 1.49kB 0.0s
=> => sha256:261da4162673b93e5c0e7700a3718d40bcc086dbf24b1ec9b54bca0b82300626 3.26MB / 3.26MB 0.3s
=> => extracting sha256:261da4162673b93e5c0e7700a3718d40bcc086dbf24b1ec9b54bca0b82300626 0.1s
=> [internal] load build context 0.0s
=> => transferring context: 6.37kB 0.0s
=> [2/9] RUN apk add --no-cache bash curl maven openjdk17 git jq libxml2-utils nodejs npm unzip 7.7s
=> [3/9] RUN npm install --global apigeelint@2.10.0 14.2s
=> [4/9] COPY tools/apigee-sackmesser /opt/devrel/tools/apigee-sackmesser 0.0s
=> [5/9] RUN mkdir /opt/apigee 0.2s
=> [6/9] RUN addgroup -S apigee && adduser -S apigee -G apigee && chown -R apigee /opt/devrel && chown -R apigee /opt/apigee 0.2s
=> [7/9] WORKDIR /opt/devrel/tools/apigee-sackmesser 0.0s
=> [8/9] RUN mvn clean -f ./cmd/deploy/pom-hybrid.xml && mvn clean -f ./cmd/deploy/pom-edge.xml 2.7s
=> [9/9] WORKDIR /opt/apigee 0.0s
=> exporting to image 0.8s
=> => exporting layers 0.8s
=> => writing image sha256:9c497b9155b7061c509d39014f30c6ad80776740aa9424b4d8ad39dac2e97d40 0.0s
=> => naming to docker.io/library/apigee-sackmesser 0.0s
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
valentinmalard@HEL-DF-JW2X7KVWNM apigee-sackmesser % And also on the github runner 💯 (Not copying the full logs, too much ^^)
---> 675b719bd1ca
Successfully built 675b719bd1ca
Successfully tagged apigee-sackmesser:latestYou good guys thanks a lot 👍
danistrebel
commented
1 year ago Thanks a lot for checking. We'll merge the PR soon.
danistrebel
commented
1 year ago never mind.. already merged 😄
Locally and also through github action I try to run the command Run ./tools/apigee-sackmesser/build.sh -t apigee-sackmesser but I get a failure at the time of running this line from dockerfile Step 3/13 : RUN npm install --global apigeelint@2.10.0 I get this issue "npm ERR! Maximum call stack size exceeded"
Below you can find all the logs i have :
Thanks in advance for your help on this.