esbuild error when trying to run Snowpack in a docker container

[vivianeasley]

First off, if you are maintainer and looking at this, thank you! Snowpack is amazing. I work at a company where we are trying integrate Snowpack. Everything has been working great but when we push up everything to Bitbucket and it tries to build a docker container and then "snowpack build" it errors out. When we run docker locally we get the same error. I've tried using webpack as an alternative but this seems like its maybe an issue during the build step with the esBuild dependency. This is what happens when you run the docker container:

0.330 yarn run v1.22.5
0.348 $ snowpack build
0.558 [snowpack] ! building source files...
0.585 /app/node_modules/esbuild/bin/esbuild: 1: /app/node_modules/esbuild/bin/esbuild: Syntax error: word unexpected (expecting ")")
0.588 [snowpack] ✘ file:///app/src/components/app.tsx
0.588 Error: The service is no longer running
0.588 at /app/node_modules/esbuild/lib/main.js:1020:33
0.588 at sendRequest (/app/node_modules/esbuild/lib/main.js:538:14)
0.588 at start (/app/node_modules/esbuild/lib/main.js:1018:13)
0.588 at Object.transform (/app/node_modules/esbuild/lib/main.js:1068:9)
0.588 at /app/node_modules/esbuild/lib/main.js:1419:55
0.588 at new Promise ()
0.588 at Object.transform (/app/node_modules/esbuild/lib/main.js:1419:14)
0.588 at Object.transform (/app/node_modules/esbuild/lib/main.js:1268:26)
0.588 at Object.load (/app/node_modules/snowpack/lib/plugins/plugin-esbuild.js:57:66)
0.588 at async runPipelineLoadStep (/app/node_modules/snowpack/lib/build/build-pipeline.js:46:28)
0.603 error Command failed with exit code 1.
0.603 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Also, this is what we are seeing from bitbucket when it gets to this same step and then errors out:

ValueError: invalid literal for int() with base 16: b''

This has been a particularly vexing and issue and any thoughts, leads, or solutions would be immensely appreciated. Thank you!

[vivianeasley]

Turns out after quite a lot of poking across multiple people, the issue was more that the version of docker for the M1 chipset was behaving quite differently than docker in the bitbucket pipeline. Looks like this has nothing to do with Snowpack and instead is an issue with M1 Docker.

[papile]

I have the same issue on M1 Docker using devcontainers in vscode