Closed dcroote closed 2 years ago
I took a quick look and I think the original problem is that node-sass
isn't installing on node 18: https://stackoverflow.com/questions/72474004/node-sass-install-error-with-node-18-version
node-sass
is deprecated so we've replaced it with sass
already, but that change is sitting on the main
branch. Have you tried using node 16? The fleek/create-react-app
docker image uses node 16 so we should probably stick to 16 in our Dockerfile as well.
I think you might have success if you:
git clone --depth=1 --branch main https://github.com/api3dao/api3-dao-dashboard.git
node:16-alpine
)docker build --tag api3-dao-dashboard .
If I do the above I no longer get a node-sass
install error, but I do get stuck on => # [4/4] Building fresh packages...
for some reason.
I have good news: all it took was pinning to node:16-alpine
- no switching to main
, no addition of python3 make g++
, and no export NODE_OPTIONS=--openssl-legacy-provider
hack. Great suggestion.
Excellent 👍
Closed by #353
Three issues. Since we advertise users should be able to build the production image, what about adding a Docker build CI Action for production push / PR / cron to alert us of Docker build issues?
Issue 1
Relates to #328. I'm on WSL2 and received the below error when trying to build the latest
production
branch image. I was able to fix this issue by borrowing from the current line in themain
branch and using:Error:
Issue 2
Then I encountered an issue with webpack / openssl that was solved with the following
yarn build
line adjusted (Solution 3 here):Error:
Issue 3
I then hit