During docker build: Syntax error: "(" unexpected

Ran into this error while running docker build for a project locally on OS X. I read in a perhaps somewhat related thread that local OS X dependencies can mix with the files that are compiled during the docker build command so I ran $ npm uninstall -g npm on my local machine. Has anyone else run into this?

[21:03:32] Using gulpfile /app/gulpfile.js [21:03:32] Starting ‘generate-assets’… [21:03:32] Starting ‘styles’… [21:03:32] Starting ‘scripts’… [21:03:32] Starting ‘vendorScripts’… [21:03:32] Starting ‘imgCompression’… [21:03:33] Finished ‘scripts’ after 303 ms [21:03:33] ‘imgCompression’ errored after 306 ms [21:03:33] Error in plugin “gulp-imagemin” Message: /app/node_modules/optipng-bin/vendor/optipng: 1: /app/node_modules/optipng-bin/vendor/optipng: Syntax error: “(” unexpected

Details: code: 2 killed: false stdout: stderr: /app/node_modules/optipng-bin/vendor/optipng: 1: /app/node_modules/optipng-bin/vendor/optipng: Syntax error: “(” unexpected

failed: true
signal: null
cmd: /app/node_modules/optipng-bin/vendor/optipng -strip all -clobber -fix -o 3 -out /tmp/d41e4654-da3c-4094-9b45-b2b08389e429 /tmp/9b181e38-4179-42c2-8c69-75bcb1320b5e
timedOut: false
fileName: /app/clientsite/static/images/clientsite_logo_500_500_red.png
domainEmitter: [object Object]
domain: [object Object]
domainThrown: false

[21:03:33] ‘generate-assets’ errored after 313 ms npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! clientsite@0.1.0 build: gulp generate-assets npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the clientsite@0.1.0 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2020-10-27T21_03_33_133Z-debug.log

[drichfield]

In my case it was simply because i had previously run an npm install on my local machine in the same app that I’m building the image from. The Dockerfile was setup to copy the entire repo into the image, which in my case, included node_modules. Deleting it before building the image and then adding a .dockerignore with the node_modules exclusion solves it.

[hyunhoRIDI]

In my case it was simply because i had previously run an npm install on my local machine in the same app that I’m building the image from. The Dockerfile was setup to copy the entire repo into the image, which in my case, included node_modules. Deleting it before building the image and then adding a .dockerignore with the node_modules exclusion solves it.

amazing. Thank you