Specify node version for fly.io deployment via wasp deploy fly deploy
Seeing this error when my server launches on fly.io
Is there a way to specify the version of node the Dockerfile uses via
wasp deploy fly deploy
?
Wasp version 0.16.32 Replies
Hi @wardbox. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the error message you're seeing, it appears that the Sharp module requires Node.js version ^18.17.0 ^20.3.0 >=21.0.0, but your Fly.io deployment is using Node.js v20.0.0, which doesn't meet these requirements.
From the knowledge sources provided, I can see that Wasp has been updating its Node.js version requirements over time. In the past, Wasp had strict Node.js version requirements (only supporting specific LTS versions), but in more recent versions (since around version 0.12), Wasp has relaxed these requirements to support Node.js 18 and above.
However, I don't see specific information in the knowledge sources about how to customize the Node.js version used in the Dockerfile generated by
wasp deploy fly deploy
.
The error you're encountering is specifically related to the Sharp module, which requires a newer version of Node.js than what's currently being used in your deployment.
You might want to:
1. Check if there's a way to modify the Dockerfile that Wasp generates before deployment
2. Contact the Wasp team through their Discord or GitHub for specific guidance on customizing the Node.js version for Fly.io deployments
3. Consider using a compatible version of Node.js locally when developing your application
Unfortunately, the knowledge sources don't contain enough information to provide a definitive solution for specifying the Node.js version in the Dockerfile used by wasp deploy fly deploy
.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @wardbox, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?downgrading to
32.6
fixed it. trying a better fix now 😄
better fix didn't work :FeelsBadMan: i tried installing the relevant version for linux musl npm install --cpu=x64 --os=linux --libc=musl sharp
no dice, still needed a higher version of node